| 1 |
On Thu, Oct 15, 2015 at 4:10 PM, Zac Medico <zmedico@g.o> wrote: |
| 2 |
> What's probably desired is to create a stage3 profile which adds |
| 3 |
> whatever extra stuff you want to @system, and to use the stage3 profile |
| 4 |
> for to build stage3. After the stage3 is built, catalyst could set some |
| 5 |
> other profile if we don't want users to have the stage3 profile by default. |
| 6 |
|
| 7 |
Unless we seed @selected with the extra stuff, it will get removed the |
| 8 |
first time the user runs --depclean, which probably isn't what we |
| 9 |
want. |
| 10 |
|
| 11 |
I'm fine with going the multi-profile route, but it seems to me that |
| 12 |
we still need some kind of initial @selected set. |
| 13 |
|
| 14 |
Basically the goal here is to give the user a bunch of useful stuff by |
| 15 |
default (specified in some way in the profile), but make it easy for |
| 16 |
the user to remove it if they wish. |
| 17 |
|
| 18 |
A side goal is to do this without adding 14 more profiles, because we |
| 19 |
don't have mixins. |
| 20 |
|
| 21 |
-- |
| 22 |
Rich |
Archives