1 |
On 12/28/11 05:14, Sven Vermeulen wrote: |
2 |
> Hi guys, |
3 |
> |
4 |
> I noticed we don't describe in the handbook that Portage can have |
5 |
> per-package environment variables (like CFLAGS) through /etc/portage/env. |
6 |
> This can be even (ab?)used to execute steps before or after specific phases |
7 |
> (based on the EBUILD_PHASE information), something I use for updating IDS |
8 |
> systems (postinst/prerm phase). |
9 |
> |
10 |
> But I'm not sure if and where in the handbook this can be positioned best. |
11 |
> The environment variable stuff could be placed in the section on |
12 |
> "Environment Variables", but is quite off from the rest of the content |
13 |
> (since the rest of that chapter has nothing really to do with Portage or |
14 |
> build environments). |
15 |
> |
16 |
> "Configuring through Variables" is probably the best location (somewhere in |
17 |
> the beginning as we talk there about Build-specific Options), but I do feel |
18 |
> that this particular feature is already more targeting advanced users, where |
19 |
> the location in the handbook somewhat suggests this for more beginner-like |
20 |
> types. |
21 |
> |
22 |
> Perhaps another section in "Working with Portage", called "Advanced Portage |
23 |
> Features" or so? This can then contain the per-package env information, but |
24 |
> also overriding profile information and perhaps others we don't talk about |
25 |
> yet. |
26 |
> |
27 |
> Any ideas on this? |
28 |
> |
29 |
> Sven |
30 |
|
31 |
Well, imho, a handbook installation is about basics and during the |
32 |
initial build, particularly for one new to gentoo, extensive |
33 |
flag settings (customization via /etc/portage) might cause more |
34 |
problems than any gains might achieve. Remember we do that the |
35 |
various profiles for the different desktop and server configs. |
36 |
|
37 |
What would be nice is to created stripped down versions of the handbook |
38 |
(on the WIKI) where the focus is more highly specialized configuration |
39 |
for the use of the newly installed (gentoo) machine. Also on the gentoo |
40 |
wiki, we can lower the bar, and let those accomplished individuals |
41 |
create something cool, and a developing admin take it over and |
42 |
maintain the document, or extend it to different hardware platforms. |
43 |
Flag customization could easily differ on different platforms. |
44 |
Why, one could even use embedded gentoo with uClib as a basis |
45 |
for a targeted, customized build of Gentoo on the new installation |
46 |
(hardware). |
47 |
|
48 |
(side note, if AMD follows through and starts offering |
49 |
ARM (A15) machines, our current handbook will be ripped |
50 |
at the seams, imho. |
51 |
|
52 |
Some examples for the WIKI: |
53 |
An Apache server: |
54 |
complete with either hardened or SElinux setup, |
55 |
including packages such as perl, python, php (or whatever mix). |
56 |
There, your customized flag settings would be focused and very |
57 |
keenly appreciated for an intermediate level gentoo admin to |
58 |
leverage. |
59 |
|
60 |
Some other intermediate level ideas for the WIKI: |
61 |
|
62 |
Light-weight workstation: |
63 |
with gui for older hardware (not Gnome or KDE) |
64 |
|
65 |
secure/encrypted mail server |
66 |
|
67 |
firewall (with DMZ for servers). |
68 |
|
69 |
transparent bridge. |
70 |
|
71 |
transparent sniffer: |
72 |
with lots of ethernet interfaces set up in stealth mode |
73 |
(taps to other secure ethernet segments for passive monitoring. |
74 |
|
75 |
|
76 |
In these (and many others exist) customization as well as minimization |
77 |
of flag settings would be of keen interest to the wider, intermediate |
78 |
gentoo community. God forbid one of the really sharp (gentoo) hacks |
79 |
share a little magic with us commoners? |
80 |
|
81 |
So keep the handbook the same but start experimenting (via the WIKI) |
82 |
on derivatives that are more targeted and focused on customizations, |
83 |
including but not limited to stringent flag settings |
84 |
|
85 |
Just my thoughts, YMMV. |
86 |
|
87 |
James |