1 |
On Tue, Jan 19, 2021 at 9:58 AM Matt Turner <mattst88@g.o> wrote: |
2 |
> |
3 |
> On Tue, Jan 19, 2021 at 6:04 AM Daniel Cordero <gentoo.catalyst@××××.ws> wrote: |
4 |
> > On Mon, Jan 18, 2021 at 03:21:52PM -0500, Matt Turner wrote: |
5 |
> > > There should be no need for custom updates, and if there are exceptional |
6 |
> > > circumstances the new --enter-chroot option can be used. |
7 |
> > > |
8 |
> > |
9 |
> > There is still a need, and if I'm reading these patches right, |
10 |
> > --enter-chroot would not satisfy that need. |
11 |
> > |
12 |
> > enter-chroot is interactive, and, depending on hardware speed, the time |
13 |
> > between kicking off the catalyst run and when the chroot shell is |
14 |
> > invoked may be some time for a human operator to monitor. |
15 |
> > |
16 |
> > It also adds non-deterministic, un-reproducible behaviour to a build. |
17 |
> > Having it in the spec file at least means it is included in a build |
18 |
> > artifact. |
19 |
> |
20 |
> Can you think of a case where update_seed would be needed? I tried, |
21 |
> and couldn't think of anything, but I might not be imaginative enough. |
22 |
> |
23 |
> My thinking is that with @changed-subslots, there's essentially no |
24 |
> need to update the seed stage further. But there have been some |
25 |
> exceptional cases that don't really fit update_seed (e.g., things that |
26 |
> cannot be fixed with emerge ...). |
27 |
|
28 |
ping? |