Re: Upgrade path w/ new compat package

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 4 Apr 2017 11:48:44 +0200, Vít Ondruch wrote:

> It is not rename .... jquery is updated and introduced new jquery2
> package. There is nothing to obsolete anywhere ....

*sigh*

It is exactly this,

  https://fedoraproject.org/wiki/Package_Renaming_Process
  https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages

because you want the new js-jquery2 package to replace the previous
js-jquery package, or else it would not satisfy existing dependencies
at all. Only with the added "Provides" as per the renaming process
it would do that.

It would also be poor form to upgrade js-jquery to something not needed
in any dependencies of installed packages and then to pull in the new
js-jquery2 to resolve those dependencies. If installed packages need v2
and not either v2 or later, js-jquery2 is introduced as a replacement
for the older js-jquery package. Without adding a proper Obsoletes tag,
multiple compat packages would pile up even if not be needed for any
dependency in installed packages.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux