| 1 |
On 26/02/18 17:24, Michael Orlitzky wrote: |
| 2 |
> On 02/26/2018 10:16 AM, Peter Humphrey wrote: |
| 3 |
>> |
| 4 |
>> Well, I'm on amd64, not ~amd64, and this morning portage wanted to remerge |
| 5 |
>> 217 packages. Removing --changed-deps reduced that to one: sys-devel/llvm. |
| 6 |
>> |
| 7 |
> |
| 8 |
> You do need to reinstall those. |
| 9 |
> |
| 10 |
> The latest (un)stable versions of automake are hard-coded in |
| 11 |
> autotools.eclass, and they wind up in the dependency string of every |
| 12 |
> ebuild that uses the eclass. It's stupid, we don't need to do it, and it |
| 13 |
> breaks all of those packages for other PMS-compliant package managers |
| 14 |
> (--changed-deps is portage-only). Sorry, we can't make people not do |
| 15 |
> this, apparently. |
| 16 |
|
| 17 |
Can't you whitelist packages like automake so that they don't trigger |
| 18 |
rebuilds? Or at least provide a configurable whitelist (for make.conf) |
| 19 |
where we can add packages that don't trigger changed-deps rebuilds? |
| 20 |
|
| 21 |
There is no reason to rebuild anything just because of an automake |
| 22 |
update. This is just madness. |
Archives