1 |
On Sun, Aug 06, 2006 at 10:39:19PM -0700, Zac Medico wrote: |
2 |
> Brian Harring wrote: |
3 |
> > On Sun, Aug 06, 2006 at 02:54:36AM -0700, Zac Medico wrote: |
4 |
> >> seems to me that we'd also have to implement use-dep matching in |
5 |
> >> order to correctly support use-dep syntax. |
6 |
> > |
7 |
> > If you were actually supporting use deps, yes. You're not |
8 |
> > however- package.use.mask is just a kludge in the (hopefully short) |
9 |
> > interim. |
10 |
> |
11 |
> It doesn't make any sense to me to have use-deps syntax without support for use-deps matching. Sorry. |
12 |
|
13 |
One question then- what's the long term plan for use deps? Both |
14 |
getting there, and transitioning to 'em? |
15 |
|
16 |
Might seem stupid, but profiles have _no_ versioning builtin, so |
17 |
anything that gets shoved in can be extremely tricky to rip out down |
18 |
the line. |
19 |
|
20 |
In other words, long term, what's the intention here? Shift over to |
21 |
package.mask with use deps (what this file is) how exactly, since the |
22 |
only way I see is when y'all get use-deps, all of that data has to be |
23 |
duplicated in package.mask and have the file flipped off in the same |
24 |
version- not really an option obviously, meaning this file stays long |
25 |
term. |
26 |
|
27 |
Hence why I'm poking on this- features are nice, but portage has a bit |
28 |
of a history as being a ball of scarily duct taped together features, |
29 |
wondering what the actual plan is here (both on the use masking and |
30 |
the forcing). |
31 |
|
32 |
So... grand plan here? |
33 |
|
34 |
~harring |