On Thu, 11 Sep 2014 13:54:07 +0200, Nikos Mavrogiannopoulos wrote: > 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. Which suggests that you need to follow the package renaming/replacing process to ensure that the "old" vpnc-script subpackage gets obsoleted, only necessary if the new vpnc-script starts with a lower %version (or a different arch), and that the old vpnc-script subpackage will be discontinued and not reintroduced with a higher EVR that would replace your new vpnc-script package. https://fedoraproject.org/wiki/Package_Renaming_Process At [1] I cannot find any %version, but the old one is < 0.5.3-24 in case you need an Obsoletes tag: http://pkgs.fedoraproject.org/cgit/vpnc.git/plain/vpnc.spec > If vpnc-script becomes a separate package (with its own repository), > does it qualify as new package? It does. It must be verified that the new package replaces the old package properly and that the old package will be discontinued. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
