On Wed, 2008-05-07 at 14:29 -0400, Deepak Bhole wrote: > A page detailing the reasons for keeping the exception is now up on the > wiki: > > http://fedoraproject.org/wiki/DeepakBhole/ReasonsForKeepingJPP Deepak, thanks for writing that up. Seth Vidal has helped me come up with a technical solution that should meet the requirements described in your document. http://skvidal.fedorapeople.org/misc/exclude-by-group/ This is a very simple yum plugin that enables the user to exclude by RPM Group tag. Since the RPM Group tag is not standardized in any way in Fedora packages (aside from the fact that it must be present), it should be possible for all JPackage RPMs in Fedora to have a unique string in the Group field (it could be JPackage, Java, jpp, Java/JPackage or GiantGilaMonster). To address your reasons: * This plugin enables the grouping operations to exclude JPackage RPMs in Fedora * This enables JPackage to use Fedora as their development OS * This enables people wishing to deploy an entire JPackage stack * By identifying JPackage in the Group field, it gives credit to the JPackage origin of these packages. * Without *jpp* in Fedora Release tags, it becomes very obvious whether a package came from Fedora repositories or JPackage repositories. Hopefully, you will agree that this plugin obsoletes the need for the JPackage naming exception in Fedora. I look forward to your feedback. Thanks, ~spot -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
