1 |
On Fri, Aug 04, 2006 at 08:46:34PM -0700, Zac Medico wrote: |
2 |
> Brian Harring wrote: |
3 |
> > On Fri, Aug 04, 2006 at 12:38:39PM -0700, Zac Medico wrote: |
4 |
> >> I haven't seen a specification for use dependencies yet, so I'm not quite sure how they'd work. |
5 |
> > cat/pkg-ver[use1,use2,-use3,use4] |
6 |
> > cat/pkg-ver[use] |
7 |
> > etc. |
8 |
> |
9 |
> Okay, so the only difference from package.use format is that whitespace is replaced by square brackets and commas? |
10 |
|
11 |
Yep- bracket/comma usage allows the atom and use reqs to bundled as |
12 |
one token. |
13 |
|
14 |
> >> Is the existing format of of use.mask bad? What about package.use? The implementation that I've proposed is a combination of these two formats that everyone is already familiar with. |
15 |
> > |
16 |
> > No... the issue is that this _is_ basically a crappy form of |
17 |
> > package.mask supporting use-deps; why use an alt syntax for it then? |
18 |
> |
19 |
> Well, no part of portage currently supports use-deps. Therefore, |
20 |
> use-deps are an alternate syntax in themselves. The implementation |
21 |
> that I've proposed uses the same type of syntax that portage already |
22 |
> uses in package.use files. |
23 |
|
24 |
use-dep syntax is usable globally however- package.use is strictly |
25 |
config file, if/when portage gains use dep, killing off the |
26 |
package.use format for the globally usable use-dep will need to occur. |
27 |
|
28 |
With that in mind, why not just do it from the get go? |
29 |
|
30 |
> > Just use what was originally intended, and at some point down the line |
31 |
> > when either portage grows use deps, or it gets replaced, folks can |
32 |
> > just copy the package.use.mask into package.mask, and wipe the file. |
33 |
> > |
34 |
> > ~harring |
35 |
> |
36 |
> Such a migration (if it ever takes place) could just as well be |
37 |
> performed by a simple conversion tool. |
38 |
Or if just using use-dep, a cat :P |
39 |
~harring |