| 1 |
On 01/22/2018 11:37 AM, Mike Gilbert wrote: |
| 2 |
>> |
| 3 |
>> If the dependencies are to remain in the eclasses, then the eclasses |
| 4 |
>> should get a new revision when those dependencies change. Afterwards, |
| 5 |
>> the consumers can be revbumped and stabilized normally to utilize the |
| 6 |
>> new eclass. |
| 7 |
> |
| 8 |
> While that sounds like the right thing to do in theory, updating all |
| 9 |
> consumers of autotools.eclass whenever a new version of automake is |
| 10 |
> stabilized is really a lot of work for very little benefit. |
| 11 |
|
| 12 |
Is now a good time to reconsider why we're manually listing stable |
| 13 |
versions of automake in autotools.eclass? |
Archives