| 1 |
On 7/10/06, Zac Medico <zmedico@g.o> wrote: |
| 2 |
> Richard Fish wrote: |
| 3 |
> > On 7/10/06, Ned Ludd <solar@g.o> wrote: |
| 4 |
> >> per pkg cflags are here already it would fall under the per |
| 5 |
> >> pkg env variables. |
| 6 |
> > |
| 7 |
> > Please forgive my stupidity, but the only place I could see to set a |
| 8 |
> > env var per package was /etc/portage/bashrc. Is that what you are |
| 9 |
> > referring to? |
| 10 |
> |
| 11 |
> You're close. There is now a per-package bashrc implementation included in $PORTDIR/profiles/base/profile.bashrc. It's kind of silly imo, when the user can simply put that same code in /etc/portage/bashrc, but this is how it is. :) |
| 12 |
|
| 13 |
Ah, thanks, I see it now. |
| 14 |
|
| 15 |
I have to say I dislike allowing this "backdoor" method to set CFLAGS, |
| 16 |
as they won't show up in emerge --info or emerge -pv <pkg>. You'd |
| 17 |
have to see the actual build output to see the nasty flags, which you |
| 18 |
might not even think to ask for if a package builds fine but crashes |
| 19 |
randomly later. |
| 20 |
|
| 21 |
-Richard |
| 22 |
-- |
| 23 |
gentoo-dev@g.o mailing list |
Archives