1 |
Duncan wrote: |
2 |
|
3 |
> The feature is somewhat limited, in that these files are sourced in the |
4 |
> bash portion of portage (basically, ebuild.sh) -- the python portion |
5 |
> knows nothing about them. |
6 |
GREAT ! |
7 |
Can I use them for switching gcc compiler etc, not just for simple |
8 |
variable settings ? |
9 |
|
10 |
And btw, is there a way to switch gcc back after emerge without changing |
11 |
ebuild file ? |
12 |
|
13 |
Or maybe there is some other mechanism to be able to compile package |
14 |
with particular gcc ? |
15 |
|
16 |
One more question: |
17 |
|
18 |
What if two or more files match the package ? |
19 |
|
20 |
Like: |
21 |
|
22 |
env/sys-kernel/vanilla-sources |
23 |
env/sys-kernel/vanilla-sources-2 |
24 |
env/sys-kernel/vanilla-sources2.6 |
25 |
env/sys-kernel/vanilla-sources-2.6.27 |
26 |
|
27 |
Do they all get included in some /un/specified order or just |
28 |
first/last/unspecified one ? |
29 |
|
30 |
|
31 |
branko |