| 1 |
>From Lisa Seelye on Saturday, 04 October, 2003: |
| 2 |
>On Sat, 2003-10-04 at 13:14, Joseph Pingenot wrote: |
| 3 |
>> Hello. |
| 4 |
>> |
| 5 |
>> I've been thinking it over, and wondering if it might well be more |
| 6 |
>> advantageous to use a file with per-package USE flags rather than one |
| 7 |
>> set of USE flags. This would allow, for instance, some packages to be |
| 8 |
>> built with certain options while keeping the same options shut off in |
| 9 |
>> other packages. |
| 10 |
>Something like /usr/portage/profiles/use.local.desc ? |
| 11 |
|
| 12 |
No, I mean changing from a global USE flags system to a system where |
| 13 |
it's clearer what USE flag is for what package. |
| 14 |
|
| 15 |
e.g. |
| 16 |
|
| 17 |
<<EOF |
| 18 |
[global] |
| 19 |
pam |
| 20 |
[ssh] |
| 21 |
nopam |
| 22 |
egd |
| 23 |
EOF |
| 24 |
|
| 25 |
(very simple sample). In this one, globally, PAM is used, but SSH disables |
| 26 |
PAM and uses the Entropy Gathering Daemon. |
| 27 |
Such a setup could furthermore be useful, because one could add things like |
| 28 |
|
| 29 |
<<EOF |
| 30 |
[ssh] |
| 31 |
defPath=/bin:/usr/bin:/usr/local/bin:/usr/local/opt/Mathematica/bin |
| 32 |
EOF |
| 33 |
|
| 34 |
to add special configuration information, in this case setting up the |
| 35 |
default path. There are other potential uses for such a system, |
| 36 |
especially since there are fairly many things which can be set at |
| 37 |
compile-time. Another example would be a spoof string for ircii and |
| 38 |
epic4 to report back as the client information string, since I (and |
| 39 |
others) are paranoid about people knowing exactly what versions of |
| 40 |
things we're using. |
| 41 |
|
| 42 |
[epic4] |
| 43 |
clientString=None of your beeswax. |
| 44 |
[ircii] |
| 45 |
clientString=None of your beeswax. |
| 46 |
|
| 47 |
Sound cool? |
| 48 |
|
| 49 |
-Joseph |
| 50 |
|
| 51 |
-- |
| 52 |
Joseph===============================================trelane@××××××××××.net |
| 53 |
"Asked by CollabNet CTO Brian Behlendorf whether Microsoft will enforce its |
| 54 |
patents against open source projects, Mundie replied, 'Yes, absolutely.' |
| 55 |
An audience member pointed out that many open source projects aren't |
| 56 |
funded and so can't afford legal representation to rival Microsoft's. 'Oh |
| 57 |
well,' said Mundie. 'Get your money, and let's go to court.' |
| 58 |
Microsoft's patents only defensive? http://swpat.ffii.org/players/microsoft |
| 59 |
|
| 60 |
-- |
| 61 |
gentoo-dev@g.o mailing list |
Archives