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