| 1 |
On 18/06/11 15:08, Ciaran McCreesh wrote: |
| 2 |
> On Sat, 18 Jun 2011 14:18:28 +0200 |
| 3 |
> justin <jlec@g.o> wrote: |
| 4 |
>> The reason why it would be beneficial to use is the pkg_pretend phase |
| 5 |
>> is simply that the checks would run at the beginning of a emerge and |
| 6 |
>> it would fail directly instead somewhere in the middle. For a single |
| 7 |
>> package it won't change much but for a huge emerge it changes the |
| 8 |
>> things. |
| 9 |
> |
| 10 |
> Hang on... What happens if someone doesn't have a fortran compiler |
| 11 |
> installed, but installs one and then installs a fortran-using package |
| 12 |
> all as part of the same group of packages? Then your pkg_pretend will |
| 13 |
> fail incorrectly. |
| 14 |
|
| 15 |
That's a serious reason to go to pkg_Setup, which ends the discusion. |
| 16 |
thanks. |
| 17 |
|
| 18 |
> |
| 19 |
> Also, you appear to be assuming that environment variable saving |
| 20 |
> carries over from pkg_pretend to later phases. It doesn't. |
| 21 |
> |
| 22 |
|
| 23 |
If I get it correctly the pretend phase is also executed when the |
| 24 |
individual packages gets emerged not only when the emerge of multiple |
| 25 |
packages is started. But the original intention of everything is that |
| 26 |
user can do FC=myFortranCompiler emerge foo. And there the FC will be |
| 27 |
preserved for every package. |
| 28 |
|
| 29 |
Thanks justin |
Archives