On Sun, Jan 21, 2018 at 11:57 PM, Michael Orlitzky <m...@gentoo.org> wrote: > On 01/21/2018 11:24 PM, Zac Medico wrote: >> >> Some eclasses like autotools.eclass and vala.eclass generate >> version/slot locked dependencies that cause the dependencies of >> inheriting ebuilds to change when the versions in the eclasses are >> updated. If possible, it would be nice to avoid this version/slot >> locking. If not possible, then what should be do? >> > > This changes the deps in stable ebuilds, and was already a no-no. > > If the dependencies are to remain in the eclasses, then the eclasses > should get a new revision when those dependencies change. Afterwards, > the consumers can be revbumped and stabilized normally to utilize the > new eclass.
While that sounds like the right thing to do in theory, updating all consumers of autotools.eclass whenever a new version of automake is stabilized is really a lot of work for very little benefit.