1 |
On Wed, 2008-12-10 at 19:30 -0600, Jeremy Olexa wrote: |
2 |
> Alan Hourihane wrote: |
3 |
> > On Thu, 2008-12-11 at 01:21 +0000, Alan Hourihane wrote: |
4 |
> >> On Thu, 2008-12-11 at 01:18 +0000, Alan Hourihane wrote: |
5 |
> >>> On Wed, 2008-12-10 at 19:15 -0600, Jeremy Olexa wrote: |
6 |
> >>>> Alan Hourihane wrote: |
7 |
> >>>>> Why do we reset EPREFIX in gcc-config - isn't it already set by the |
8 |
> >>>>> SHELL ? |
9 |
> >>>>> |
10 |
> >>>>> Alan. |
11 |
> >>>>> |
12 |
> >>>>> |
13 |
> >>>> It is not guarenteed to be set in the shell. Although, I am not against |
14 |
> >>>> it. Maybe it could/should be set in etc/env.d/00basic ? |
15 |
> >>> So where is it guaranteed to be set ?? Otherwise a lot of ebuilds would |
16 |
> >>> break ? |
17 |
> >> I'll mention I thought the right way was to use "startprefix" to enter |
18 |
> >> prefix which does set it via the SHELL. |
19 |
> > |
20 |
> > And even then, we needn't reset it in gcc-config which was the real |
21 |
> > question in the thread, so it should be removed. |
22 |
> > |
23 |
> > Alan. |
24 |
> > |
25 |
> > |
26 |
> |
27 |
> Woa, hold on. Formalize your thoughts before hitting send ;) |
28 |
|
29 |
There's always something else to comment on :-) |
30 |
|
31 |
> EPREFIX is passed to portage via a configure call. So, portage always |
32 |
> knows about EPREFIX. There is more than one way to enter your prefix |
33 |
> environment and we should not break on purpose if users prefer to not |
34 |
> use startprefix.. Off hand, I don't know how EPREFIX is used in |
35 |
> gcc-config (no access to my prefix during off hours), so I will defer |
36 |
> answering that for now, just wanted to clarify the above point. |
37 |
|
38 |
binutils-config is the same and sets it's own EPREFIX based on what |
39 |
portage passes down to it when emerging. |
40 |
|
41 |
I'm wondering how many other scripts do this now. |
42 |
|
43 |
Alan. |