On 01/22/2018 11:37 AM, Mike Gilbert wrote: >> >> 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.
Is now a good time to reconsider why we're manually listing stable versions of automake in autotools.eclass?
