Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=542715 --- Comment #9 from Kalev Lember <kalev@xxxxxxxxxxxx> 2010-03-19 04:14:17 EDT --- (In reply to comment #8) > I don't think I should add "Requires: nautilus-python >= 0.5.2", since it works > with older nautilus-python on 32-bit systems. I actually think it would be better to have versioned Requires >= 0.5.2: this way people who haven't applied all updates can just do "yum install rabbitvcs" and the new nautilus-python 0.5.2 automatically gets pulled in. It's pretty much required on x86_64, and having that require doesn't make anything worse for people who run 32-bit Fedora. > There's been one gigantic packaging change as of 0.13, and I'm not sure if I > handled it properly. > > Rabbitvcs is now handing out an individual tarball for each plugin, so I added > a source for each plugin, to generate subpackages. Otherwise, we'd have to get > a basically useless rabbitvcs package, then approve each individual rabbitvcs > plugin... > > Feedback regarding this change would be very welcome. I'm not sure why they would want to split out tarballs like that. The split would make sense if the components were independent, but right now they aren't: you probably need to keep all the tarballs strictly at the same version. Also, most of the plugin tarballs only contain ONE python file + readme, which in my opinion should just get a separate subdirectory in the main tarball. Maybe you could contact upstream and ask them about this change? I'm pretty sure it'd make life easier for you if they distributed it all in one tarball. Alternatively, if they want to keep the split tarballs, maybe they could also release a rabbitvcs-0.13.tgz with all the plugins bundled together, but keep the split ones too? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review