Le Jeu 1 février 2007 13:30, Ralf Corsepius a écrit : > * Empower me with arguments why Fedora's java needs the jpp suffix? > * Empower me with arguments why jpp package can't be merge into Fedora? This has been answered many times already. 1. There is already a bidirectionnal merge process between Fedora and JPP (Fedora gets the results of JPP work, JPP gets the results of Fedora work, and everyone cross-checks the other). 2. The java team can "fix" a jpp package at the jpp level any time they need to. Any other Fedora contributor can get jpp access now by demontrating packaging skills, if he doesn't want to rely on Fernando Nasser 3. JPP is not a drag - it will go as fast and do as strict packaging as its contributors (including the fedora java team) allow. The "worst" scenarii that can happen are : - the Fedora Java team doing all the work there, at which point JPP policy would effectively be Fedora policy - the Fedora Java team offloading all the work @jpp, at which point JPP policy may not be aligned with Fedora policy at all but Fedora would get all its java packaging for free 4. Pulling packages in-Fedora without the back-merging means losing the packaging & review work that happens @jpp, and getting cross-distro namespace divergence for zero wins The jpp suffix is there to help the workflow of the java team by identifying packages participating to this process (because we've refused to fix rpm groups and only provided a comps alternative the anaconda guys do not want to share) -- Nicolas Mailhot -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
