| 1 |
David CHANIAL wrote: |
| 2 |
> Le Jeudi 08 Juin 2006 16:39, Michael Stewart (vericgar) a écrit : |
| 3 |
>> For now, if you need to change those variables, you need to move the |
| 4 |
>> ebuild to an overlay and modify it to your needs. In the future you |
| 5 |
>> won't have to. |
| 6 |
> |
| 7 |
> i understand, |
| 8 |
> |
| 9 |
> but we are not speaking for a feature now, juste for an environnement variable |
| 10 |
> which will help many admin to dont have to maintain apche in overlay |
| 11 |
> |
| 12 |
> and |
| 13 |
> |
| 14 |
> the "noobs" see no differences |
| 15 |
> |
| 16 |
> i post a bug. |
| 17 |
> |
| 18 |
|
| 19 |
There is already a bug for this issue. http://bugs.gentoo.org/66397 |
| 20 |
|
| 21 |
Environment variables are problematic because they are not stored and |
| 22 |
remembered when portage upgrades the package. You will have to set the |
| 23 |
environment variable every time manually for it to work. suexec-config |
| 24 |
is the better, and correct, solution. If you are unable to wait until it |
| 25 |
is backported to 1.3 or 2.0, your best option is to use an overlay. |
| 26 |
|
| 27 |
-- |
| 28 |
Michael Stewart vericgar@g.o |
| 29 |
Gentoo Developer http://dev.gentoo.org/~vericgar |
| 30 |
|
| 31 |
GnuPG Key ID 0x08614788 available on http://pgp.mit.edu |
| 32 |
-- |
Archives