Re: [gentoo-dev] You currently cannot smoothly upgrade a 4 months old Gentoo system

[Alec Warner]

On Wed, Nov 3, 2021 at 2:50 PM Andreas K. Huettel <dilfridge@g.o> wrote:
>
> Am Mittwoch, 3. November 2021, 22:39:41 CET schrieb Ulrich Mueller:
> > >>>>> On Wed, 03 Nov 2021, Andreas K Huettel wrote:
> >
> > > The mistake was to allow the use of EAPI=8 too early. In the future,
> > > we should have a new EAPI supported by portage for at least some
> > > months before the EAPI is even used in the main tree. Not even
> > > speaking about stable here.
> >
> > I tend to disagree. Adding an ebuild with a new EAPI cannot break
> > anything, because it will simply be invisible to old package managers.
>
> Except that you need to keep track of version dependencies across the whole
> tree.
>
> So, yes, this is in principle correct, and in practice with our current
> tooling more or less impossible to do reliably.

I think the obvious easy solution here is to run a CI that is using
older stuff, and report problems when commits break that.

It's less clear what to do about it though; the problems Whissi
raised.. it's not like we didn't know about them (they were known),
but we chose not to do anything about it?
Or we learned about them too late (and figured the majority of users
had seen it; so fixing them was not necessary?)

-A

>
> [Part of the output Whissi pasted was (more or less) that a Perl upgrade
> required a rebuild of Perl modules. Unfortunately, even a single one that
> is not available for rebuild makes the emerge bail out.]
>
>
> --
> Andreas K. Hüttel
> dilfridge@g.o
> Gentoo Linux developer
> (council, toolchain, base-system, perl, libreoffice)