Gentoo Archives: gentoo-catalyst

From: Matt Turner <mattst88@g.o>
To: gentoo-catalyst@l.g.o
Subject: Re: [gentoo-catalyst] [PATCH 11/11] catalyst: Remove update_seed spec option
Date: Fri, 22 Jan 2021 00:05:08
Message-Id: CAEdQ38F=_y1TWndPd7bmy-gh7jPgxTwDHyE8rUj28O6gbiGVWg@mail.gmail.com
In Reply to: Re: [gentoo-catalyst] [PATCH 11/11] catalyst: Remove update_seed spec option by Daniel Cordero
1 On Thu, Jan 21, 2021 at 5:20 AM Daniel Cordero <gentoo.catalyst@××××.ws> wrote:
2 >
3 > On Tue, Jan 19, 2021 at 09:58:15AM -0500, Matt Turner wrote:
4 > > On Tue, Jan 19, 2021 at 6:04 AM Daniel Cordero wrote:
5 > > > On Mon, Jan 18, 2021 at 03:21:52PM -0500, Matt Turner wrote:
6 > > > > There should be no need for custom updates, and if there are exceptional
7 > > > > circumstances the new --enter-chroot option can be used.
8 > > > >
9 > > >
10 > > > There is still a need, and if I'm reading these patches right,
11 > > > --enter-chroot would not satisfy that need.
12 > > >
13 > > > enter-chroot is interactive, and, depending on hardware speed, the time
14 > > > between kicking off the catalyst run and when the chroot shell is
15 > > > invoked may be some time for a human operator to monitor.
16 > > >
17 > > > It also adds non-deterministic, un-reproducible behaviour to a build.
18 > > > Having it in the spec file at least means it is included in a build
19 > > > artifact.
20 > >
21 > > Can you think of a case where update_seed would be needed? I tried,
22 > > and couldn't think of anything, but I might not be imaginative enough.
23 > >
24 > > My thinking is that with @changed-subslots, there's essentially no
25 > > need to update the seed stage further. But there have been some
26 > > exceptional cases that don't really fit update_seed (e.g., things that
27 > > cannot be fixed with emerge ...).
28 >
29 > update_seed has been very useful when dealing with perl/python version
30 > upgrades, where large swathes of packages need to be updated at the same
31 > time. I'm not sure if @changed-subslots has in any way resolved this,
32 > but it's convenient to have an override.
33
34 Okay, thanks. I'll do some testing in these areas.
35
36 > Another example was a recent bash/readline update, where the stage3 had
37 > readline.so.5 and built the new stage1 bash against that, but installed
38 > readline.so.6 into the stage1root, hence the stage2 build was broken.
39
40 This is *exactly* the situation @changed-subslots is for. Please read
41 the commit message in 05/11.