1 |
On 07/30/2010 09:26 AM, Mark David Dumlao wrote: |
2 |
> On Fri, Jul 30, 2010 at 11:51 PM, Bill Longman <bill.longman@×××××.com> wrote: |
3 |
>> The profile affects the default USE settings. This is a very important |
4 |
>> Gentoo concept. |
5 |
> |
6 |
> emerge --info eix on both machines: |
7 |
> |
8 |
> PC: |
9 |
> app-portage/eix-0.20.5 was built with the following: |
10 |
> USE="bzip2 (multilib) nls sqlite -debug -doc -hardened -optimization |
11 |
> -strong-optimization -tools" |
12 |
> LDFLAGS="-Wl,-O1" |
13 |
> |
14 |
> server: |
15 |
> app-portage/eix-0.20.5 was built with the following: |
16 |
> USE="bzip2 nls sqlite -debug -doc -hardened -optimization |
17 |
> -strong-optimization -tools" |
18 |
> LDFLAGS="-Wl,-O1" |
19 |
> |
20 |
> |
21 |
> The only difference between the USE flags of both machines is that my |
22 |
> local eix was built with multilib. I don't know any documentation |
23 |
> references that say how that should affect eix output settings, which |
24 |
> shouldn't be related. |
25 |
> |
26 |
> Just to clarify, emerge detects that the packages are keyworded on |
27 |
> both machines. It's just not being outputted by eix. And there's no |
28 |
> reason why multilib should cause eix to change the output settings. |
29 |
|
30 |
I mean to say that the profile sets the *global* USE settings. If you |
31 |
were to compare "euse -i" between the two machines, you would see that |
32 |
some flags are "+D" and some are "+C", for instance. The ones that are |
33 |
set by the profile are "+D". If you peruse the portage/profiles you'll |
34 |
see that the make.defaults files are setting different USE values. Not |
35 |
to mention that you are on different architectures between the two, so |
36 |
some packages will be masked and some not depending upon the |
37 |
architecture. It's not a matter of how eix was built, it's a matter of |
38 |
the configuration of the host. |
39 |
|
40 |
Is that what you were trying to resolve? Or do I not understand your |
41 |
question? Can you put a package mask in just *any* file below |
42 |
package.keywords/ and as long as it matches it will be valid? |