1 |
I tried to create this myself and nothing terrible happened. First, I |
2 |
created the new directory, |
3 |
|
4 |
profiles/default/linux/amd64/17.0/hardened/no-multilib (1) |
5 |
|
6 |
So, first question: is there a preference between the two choices there, |
7 |
either "17.0/hardened/no-multilib" or "17.0/no-multilib/hardened"? |
8 |
|
9 |
In the new directory (1), I created an "eapi" file containing "5", and a |
10 |
"parent" file containing |
11 |
|
12 |
../../no-multilib |
13 |
../../../../../../features/hardened/amd64 |
14 |
|
15 |
I considered using "features/hardened/amd64/no-multilib" as a parent, |
16 |
but it doesn't look like anything else is doing so. So my second |
17 |
question is: is "features/hardened/amd64/no-multilib" unused? And/or |
18 |
should I be using it? |
19 |
|
20 |
Finally, I added |
21 |
|
22 |
amd64 default/linux/amd64/17.0/hardened/no-multilib dev |
23 |
|
24 |
to profiles.desc. After eselecting the new profile, "emerge -uDN @world" |
25 |
turns up no changes (from my old no-multilib profile). |