-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/11/2014 07:54 AM, Nikos Mavrogiannopoulos wrote: > On Thu, 2014-09-11 at 12:25 +0200, Michael Schwendt wrote: >> On Thu, 11 Sep 2014 12:15:49 +0200, Nikos Mavrogiannopoulos >> wrote: >> >>> Hello, There is a package which includes a subpackage that I'd >>> like it split as a proper package (possibly with different >>> maintainers). Is there some special process for that or does it >>> have to follow the full process for new packages as in [0]? >>> >>> regards, Nikos >>> >>> [0]. >>> https://fedoraproject.org/wiki/New_package_process_for_existing_contributors >> >> >>> You could/should have given more details, which would make it easier to >> answer. > > I'd like to split vpnc-script from vpnc [0], but I don't maintain > the package, so I omitted the details. Anyway the issue is, that > vpnc-script which has a different upstream [1] than vpnc, is used > by both vpnc and openconnect, and is part of the vpnc package. For > that I'd like it split from vpnc and being a separate package, so I > can help maintain it without maintaining vpnc which I have no idea > about (the issue started when vpnc was not in epel7 and that > prevented openconnect from being there). > > [0]. https://bugzilla.redhat.com/show_bug.cgi?id=1128147 [1]. > http://git.infradead.org/users/dwmw2/vpnc-scripts.git/blob_plain/HEAD:/vpnc-script > > >> Usually, everything from one _source tarball_ is included in a >> _single_ src.rpm, so you split the build into subpackages. Once >> upstream splits off something into a separate tarball, it may be >> time to create another src.rpm for it. There is no strict >> requirement to do so, however, because RPM can handle multiple >> source archives per src.rpm. It may be more convenient to create >> multiple src.rpm packages depending on how often the individual >> pieces are updated/upgraded/rebuilt. And yes, [0] applies to new >> packages. > > Ok, but on this case we have both vpnc and vpnc-script from > vpnc.spec. If vpnc-script becomes a separate package (with its own > repository), does it qualify as new package? If not (as it is > already there) what would be the process of creating a new package > repository for it? > Yes, it qualifies as a new package and must go through the new-package process. You also want to coordinate with the owner of the vpnc package and make sure that both of your changes land at the same time (in the case of stable or branched Fedora, that probably means putting them in the same Bodhi update; for Rawhide it means building them on the same day). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQRjuMACgkQeiVVYja6o6OP9gCbBaBuc8yZ0VzBWV1KJzgEqzfn MMEAoLIB9u7lGVxvxfcawAbOO1f/7z1K =rc4W -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
