1 |
On 6/22/09, James <wireless@×××××××××××.com> wrote: |
2 |
> Arttu V. <arttuv69 <at> gmail.com> writes: |
3 |
> |
4 |
>> More reading: ebuild(5)" |
5 |
> |
6 |
> Ah, ok so there is not restriction on using any of the |
7 |
> the boolean operators in any config file underneath |
8 |
> /etc/portage? as section 5 does not mention any.... |
9 |
|
10 |
Well, for those files that are actually supposed to contain DEPEND |
11 |
atoms that is probably true. I haven't checked the whole man page and |
12 |
all files it lists to see if it places any restrictions on some |
13 |
specific files therein, so I'm a bit timid to claim full "no limits" |
14 |
either. But for package.keywords it didn't mention any limits and I'd |
15 |
believe the others don't have them either. :) |
16 |
|
17 |
Still, the best identifier of the allowed syntax is probably portage |
18 |
itself. Make a typo in files under /etc/portage and portage will tell |
19 |
you next time you emerge -pv something or emerge -av something. |
20 |
|
21 |
And it also breaks in a quite predictable fashion when it reads your |
22 |
typos in those files: it will just drop the lines it doesn't |
23 |
understand (while also printing warning messages) and then dutifully |
24 |
proceed to next line. So if ever in doubt, you can try it and see what |
25 |
portage's parser thinks about your "fuzz-test". :) |
26 |
|
27 |
> This is my (mis)conception, although, as you have suggest, |
28 |
> there are (gentoo) cultural norms that do suggest |
29 |
> certain boolean operations should not be used, |
30 |
> in say for example, package.keywords? |
31 |
|
32 |
Not sure if by cultural norms you're referring to something I'd rather |
33 |
label as "best practices"? :) |
34 |
|
35 |
But then again, there are best practices for bleeding edge folks and |
36 |
best practices for "stability is paramount" folks and they may |
37 |
overlap, but most likely they aren't quite the same. |
38 |
|
39 |
> I'm mostly running stable with exceptions being enabled |
40 |
> via the /etc/portage file structure. Usually it's small, |
41 |
> but now with kde4, BLOAT is my modus operandi, |
42 |
> not by choice...... |
43 |
|
44 |
Then, again, you probably don't want the >= as it will unmask the |
45 |
latest testing version currently available, plus in future any new |
46 |
testing grade versions as they get added to portage tree. What you |
47 |
want is either = or ~. (And do note that ~ at the front of a DEPEND |
48 |
atom means a different thing from the testing keyword in ~arch). |
49 |
|
50 |
But it is all up to you to decide, you're the commander'n'chief of |
51 |
your own boxen. |
52 |
|
53 |
-- |
54 |
Arttu V. |