Thanks for the update and the work on the 23.0 profiles. :)
Most 17.x profiles have been downgraded to "exp".I could imagine there is a reason to downgrade those back to 'exp',
could you elaborate a bit on that?
Isn't it bit strange that a 'stable' profiles gets downgraded back to
'exp'? Then again, I am not sure about the implications of this nor
about the rationale behind it.
However, I also notice that there is a outstanding PR that reverts
that [1]. Maybe we should introduce a new state 'oldstable' or so?
I see no way of migrating to 23.0 profile because of not-recompilable packages that are installed (over 4 years) which block --emptytree,
and do not wish to be forced to migrate to merged-usr on an openrc box without a compelling need (on principle).
Will patching back the 17.0 profile files into the portage tree if and
when they are removed work?
Are there any options at all for this situation (like freezing the the
last supported tree protecting it from emerge-syncs, and using an
overlay for further updates?)
Am Sonntag, 7. April 2024, 14:51:55 CEST schrieb Michael Orlitzky:
[R]emarkably bad timing. How it looks: Gentoo's response to the xz
incident is to have me rebuild my entire system with everything that
could possibly be linked to liblzma, linked to liblzma. Even on the
hardened profiles, and with no easy way to prevent it.
Well, we're now working with the best-audited compression library ever,
I guess.
tl;dr can we turn them back off in the profile? In any scenario where
they are beneficial, there's a better place to put them.
Easily doable with lzma, if there is consensus for it.
Slightly more complex for zstd since this affects gcc and binutils.
Still doable though.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 488 |
Nodes: | 16 (3 / 13) |
Uptime: | 08:40:33 |
Calls: | 9,664 |
Calls today: | 6 |
Files: | 13,711 |
Messages: | 6,167,107 |
Posted today: | 2 |