You're welcome. Putting in Obsoletes/Provides should be the "regular fashion" when merging or EOL'ing pkgs. It makes things really easier to maintain when you have to do an in-release update, e.g.: needing to fix security issues or serious bugs. YUM will purge the merged-in pkg itself and user's system keeps no leaves and there will be no possible broken deps on upgrading to the new in-release-version. The other way round it makes maintaining dependend pkgs even easier, because things won't break caused by missing deps and having to look how to get them resolved properly again. I'm not sure how FEDUP handles such cases on release updates, but I'm sure Obsoletes/Provides will make things smother in such senarios, too. At least it will help to cleanup otherwise kept leave-pkgs. And don't forget to put in proper O/P into possible -devel-pkgs, too. Cheers, Björn Am Sonntag, den 12.05.2013, 13:29 +0100 schrieb Gerard Ryan: > > ...<snip> > > Thanks for the replies guys. It's the second scenario in what you've > mentioned Björn, there's pkgfoo and pkgfoo-split. The reason I was > asking was because I was thinking along the lines of what Jon says -- > that maybe obsoletes/provides can be skipped. I guess since it's my > first time EOL'ing a package, there's no harm in me explicitly putting > them in, just to make sure. > > Thanks again, > Gerard. > -- > packaging mailing list > packaging@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/packaging -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
