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