Re: policy on changes in or introduction of new dependencies

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

 



On 02/23/2017 02:23 AM, Dominik 'Rathann' Mierzejewski wrote:
On Thursday, 23 February 2017 at 00:08, Adam Williamson wrote:
On Wed, 2017-02-22 at 22:53 +0100, Dominik 'Rathann' Mierzejewski
wrote:
Dear Fedora developers,
there have been a number of examples where an update in a stable branch
brought in new dependencies and in significant numbers. The most recent
case was discussed on this list even today:
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/BVUZWJYW2UVO53EZ2G2ALAQPU5PLDJZR/

That discussion was about Rawhide. Not about a stable release.

True, but the issue is the same. New or changed dependencies cause
problems.

Not quite. This only applies to "weak deps".

New "strong deps" or "changed deps" are should to solve problems, otherwise there would not be any need for changes.

The proposed policy change talks about both rawhide and stable branches.
I consider your proposal to be unnecessary.

Ralf
_______________________________________________
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