| 1 |
Olivier Fisette wrote: |
| 2 |
|
| 3 |
> A file named "/etc/portage/package.env" could contain entries such as: |
| 4 |
> |
| 5 |
> app-office/openoffice lang_ru |
| 6 |
> |
| 7 |
>>=app-sci/emboss-2.8.0 icc |
| 8 |
> |
| 9 |
> =app-sci/pymol-0.95* gcc_low_opt |
| 10 |
Agree, support for version is also important, as for group, because we |
| 11 |
have some packages with the name but in dfifferent groups. |
| 12 |
|
| 13 |
> If we wanted to make things even easier to configure, we could have something |
| 14 |
> like the following in "/etc/portage/package.env": |
| 15 |
> |
| 16 |
> =app-sci/pymol-0.95* [ CC="gcc" CFLAGS="-O1" ] |
| 17 |
> |
| 18 |
> ... were a keyword is replaced by a delimited short bash script that would be |
| 19 |
> sourced to provide per package env vars. This would avoid having to create |
| 20 |
> files in "/etc/portage/env.d" which target only one package. |
| 21 |
Anyway, if we going to include both, files and inlined vars, we have to |
| 22 |
have a bit complicated parser of lines. In such case we even don't need |
| 23 |
[], we can leave as |
| 24 |
=app-sci/pymol-0.95* gcc_low_opt CC="gcc" |
| 25 |
"=" specify enough that we have inlined expression. |
| 26 |
|
| 27 |
-- |
| 28 |
Anton Starikov |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives