| 1 |
Am Mittwoch, 3. November 2021, 22:39:41 CET schrieb Ulrich Mueller: |
| 2 |
> >>>>> On Wed, 03 Nov 2021, Andreas K Huettel wrote: |
| 3 |
> |
| 4 |
> > The mistake was to allow the use of EAPI=8 too early. In the future, |
| 5 |
> > we should have a new EAPI supported by portage for at least some |
| 6 |
> > months before the EAPI is even used in the main tree. Not even |
| 7 |
> > speaking about stable here. |
| 8 |
> |
| 9 |
> I tend to disagree. Adding an ebuild with a new EAPI cannot break |
| 10 |
> anything, because it will simply be invisible to old package managers. |
| 11 |
|
| 12 |
Except that you need to keep track of version dependencies across the whole |
| 13 |
tree. |
| 14 |
|
| 15 |
So, yes, this is in principle correct, and in practice with our current |
| 16 |
tooling more or less impossible to do reliably. |
| 17 |
|
| 18 |
[Part of the output Whissi pasted was (more or less) that a Perl upgrade |
| 19 |
required a rebuild of Perl modules. Unfortunately, even a single one that |
| 20 |
is not available for rebuild makes the emerge bail out.] |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Andreas K. Hüttel |
| 25 |
dilfridge@g.o |
| 26 |
Gentoo Linux developer |
| 27 |
(council, toolchain, base-system, perl, libreoffice) |
Archives