1 |
Hello! |
2 |
|
3 |
I really do not understand how these cascading profiles should work?! |
4 |
|
5 |
My imagination says: |
6 |
|
7 |
put into base/make.defaults |
8 |
GRP_STAGE23_USE="${STAGE1_USE} berkdb ncurses readline zlib" |
9 |
USE="${GRP_STAGE23_USE} _GEN_USE_" |
10 |
FEATURES="_GEN_FEATURES_" |
11 |
ACCEPT_KEYWORDS="${ARCH}" /* are there cases, where ARCH!=ACCEPT_KEYWORDS */ |
12 |
|
13 |
put into uclibc/make.defaults generic stuff (parent shows to ../base) |
14 |
|
15 |
STAGE1_USE=uclibc |
16 |
USE="_UC_USE_" /* only uclibc specific use flags */ |
17 |
FEATURES="_UC_FEATURES_" /* only uclibc generic feature */ |
18 |
|
19 |
put in uclibc/arch/make.defaults |
20 |
|
21 |
ARCH=arch |
22 |
STAGE1_USE="_ARCH_STAGE1_" |
23 |
ENDIAN/... arch specific settings |
24 |
FEATURES="_ARCH_FEATURES_" /* only arch specific features if any */ |
25 |
USE="_ARCH_USE_" /* only arch specific flags if any */ |
26 |
|
27 |
put into uclibc/arch/hardened/make.defaults |
28 |
|
29 |
STAGE1_USE="crypt hardened pic pie ssl tcpd" |
30 |
FEATURES="_HARDENED_FEATURES_" /* only hardened specific features if any */ |
31 |
|
32 |
the result of cascading (emerge info) should provide, if profile set to |
33 |
uclibc/arch/hardened: |
34 |
ARCH=arch |
35 |
ACCEPT_KEYWORDS=arch |
36 |
# internal, not shown by info |
37 |
#STAGE1_USE="uclibc crypt hardened pic pie ssl tcpd _ARCH_STAGE1_" |
38 |
#GRP_STAGE23_USE="${STAGE1_USE_as_above} berkdb ncurses readline zlib" |
39 |
USE="${GRP_STAGE23_USE_as_above} _GEN_USE_ _UC_USE_ _ARCH_USE_" |
40 |
FEATURES="_GEN_FEATURES_ _UC_FEATURES_ _ARCH_FEATURES_ _HARDENED_FEATURES_" |
41 |
|
42 |
and we haven't written anything twice |
43 |
|
44 |
Does it work like this or not? |
45 |
If yes, why using lot of redundancy in these files? |
46 |
|
47 |
Peter |
48 |
|
49 |
-- |
50 |
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2 |
51 |
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2 |
52 |
|
53 |
|
54 |
-- |
55 |
gentoo-embedded@g.o mailing list |