| 1 |
> Dilfridge had a proposal to ensure 3/6/12 month old systems could still |
| 2 |
> upgrade, and I'm wondering if this could break those systems. |
| 3 |
> |
| 4 |
> There are 3 commits in the last year that finally removed the EAPI 5/6 |
| 5 |
> toolchain consumers: |
| 6 |
> 486b77ab8d28c5bfd5a4bdfc5f9a5f432ffde563 |
| 7 |
> b0a39e54065f7eda2dfc719ec05e270fa7e23e38 |
| 8 |
> 26f684adecb5b9135f9eba9f1b63c83e3d5e5722 |
| 9 |
> |
| 10 |
> The latest of those was in September 2021. |
| 11 |
> |
| 12 |
> Do we need to wait X months after those removals, to be able to commit |
| 13 |
> this change? |
| 14 |
|
| 15 |
Hmm. Portage saves and reuses the ebuild environment, so each installed |
| 16 |
package has its phases and related eclass code stored. |
| 17 |
|
| 18 |
Which means this is probably fine, since |
| 19 |
1) after syncing, the ebuilds are gone, so you'll never be able to rebuild |
| 20 |
the consumer |
| 21 |
2) and unmerging the consumer is done using the saved environment. |
| 22 |
|
| 23 |
More opinions welcome... |
| 24 |
|
| 25 |
-- |
| 26 |
Andreas K. Hüttel |
| 27 |
dilfridge@g.o |
| 28 |
Gentoo Linux developer |
| 29 |
(council, toolchain, base-system, perl, libreoffice) |
Archives