| 1 |
Kevin F. Quinn wrote: |
| 2 |
> Aside from that, what you're really after is per-package CFLAGS (or |
| 3 |
> more generally, per-package FEATURES) which is a long-standing portage |
| 4 |
> feature request. You can do it via a bashrc script |
| 5 |
> (in /etc/portage/bashrc) although it's not 100% - bashrc scripts are not |
| 6 |
> sourced in all phases of emerge (in particular, fetch), although they |
| 7 |
> are for the ones you're most likely to care about. |
| 8 |
|
| 9 |
per package env vars are supported through the base profile.bashrc. You |
| 10 |
don't have to clutter /etc/portage/bashrc, you can just do e.g. |
| 11 |
|
| 12 |
cat > /etc/portage/env/app-foo/bar << EOF |
| 13 |
CFLAGS="-O -march=k8 -pipe" |
| 14 |
CXXFLAGS="${CFLAGS}" |
| 15 |
EOF |
| 16 |
|
| 17 |
And it will set C(XX)FLAGS for app-foo/bar based on that. |
| 18 |
/etc/portage/env/app-foo/bar-1.0 and /etc/portage/env/app-foo/bar-1.0-r1 |
| 19 |
would also work. |
| 20 |
|
| 21 |
That being said, "fetch" is not a phase, that's why there are no hooks |
| 22 |
for it. |
| 23 |
|
| 24 |
-- |
| 25 |
Kind Regards, |
| 26 |
|
| 27 |
Simon Stelling |
| 28 |
Gentoo/AMD64 developer |
| 29 |
-- |
| 30 |
gentoo-amd64@g.o mailing list |
Archives