1 |
On Tue, 14 Aug 2012 14:55:47 -0700 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
> It seems like there's some confusion here. Approving a new EAPI and |
4 |
> deciding to use a new EAPI in a given profile are two entirely |
5 |
> different things. If we want to us a new EAPI in a profile, we just |
6 |
> have to deploy it such that users are only exposed to that profile |
7 |
> when they consciously running `eselect profile` (and they can always |
8 |
> revert back to the previous profile if it turns out that their |
9 |
> installed package manager doesn't support the new profile). |
10 |
|
11 |
There's still the issue that we haven't decided what [use] deps do when |
12 |
they show up in profile files. We were sticking at 1 until we worked |
13 |
that out. |
14 |
|
15 |
(Personally I'm in favour of just not allowing use deps anywhere in |
16 |
profiles, and requiring package manglers to enforce it.) |
17 |
|
18 |
-- |
19 |
Ciaran McCreesh |