1 |
On Fri, 2007-09-21 at 17:45 -0400, Mike Frysinger wrote: |
2 |
> the compromise is simple: catalyst runs --config at the end of stage3 for |
3 |
> appropriate packages, but as to what those things actually do is left in the |
4 |
> ebuilds. |
5 |
|
6 |
I've already stated my preference for not doing *anything* outside of |
7 |
merging packages in the stages. Were this >stage3, I wouldn't care. |
8 |
Anyway, I'd much rather leave everything as it is now than add the |
9 |
emerge --config stuff. You're free to add it to the ebuilds, of course, |
10 |
which would satisfy the people that want it, but I would prefer not add |
11 |
it to the stages, even if it is documented in the Handbook, as it isn't |
12 |
required. Basically, I'd rather we either throw it into the earlier |
13 |
stages, or not do it at all. You've given good reason on why, while |
14 |
technically feasible since we're only caring about bash at this time, it |
15 |
is still a bad idea as it opens us up to yet another slippery slope. I |
16 |
completely see your point, which is why I'm taking the stance that |
17 |
things are best left as they are now. |
18 |
|
19 |
-- |
20 |
Chris Gianelloni |
21 |
Release Engineering Strategic Lead |
22 |
Alpha/AMD64/x86 Architecture Teams |
23 |
Games Developer/Council Member/Foundation Trustee |
24 |
Gentoo Foundation |