1 |
Hi guys, |
2 |
|
3 |
I noticed we don't describe in the handbook that Portage can have |
4 |
per-package environment variables (like CFLAGS) through /etc/portage/env. |
5 |
This can be even (ab?)used to execute steps before or after specific phases |
6 |
(based on the EBUILD_PHASE information), something I use for updating IDS |
7 |
systems (postinst/prerm phase). |
8 |
|
9 |
But I'm not sure if and where in the handbook this can be positioned best. |
10 |
The environment variable stuff could be placed in the section on |
11 |
"Environment Variables", but is quite off from the rest of the content |
12 |
(since the rest of that chapter has nothing really to do with Portage or |
13 |
build environments). |
14 |
|
15 |
"Configuring through Variables" is probably the best location (somewhere in |
16 |
the beginning as we talk there about Build-specific Options), but I do feel |
17 |
that this particular feature is already more targeting advanced users, where |
18 |
the location in the handbook somewhat suggests this for more beginner-like |
19 |
types. |
20 |
|
21 |
Perhaps another section in "Working with Portage", called "Advanced Portage |
22 |
Features" or so? This can then contain the per-package env information, but |
23 |
also overriding profile information and perhaps others we don't talk about |
24 |
yet. |
25 |
|
26 |
Any ideas on this? |
27 |
|
28 |
Sven |