1 |
Hello |
2 |
|
3 |
Background: |
4 |
As a minimalist I'm trying to ferret out the differences in some of the more |
5 |
minimal profiles versus potential embedded profiles, across several |
6 |
different architectures: (arm32, arm64 x63_32 x86_64 ppc etc). I am also |
7 |
quite curious to find a tool that will clearly list the complete set of |
8 |
packages a given (eselected) profile will yield and the best ways to |
9 |
customize that list of minimal (critical) packages. |
10 |
|
11 |
|
12 |
|
13 |
So in /etc/portage/profiles, we have lots of good information. For example |
14 |
the 'base' dir currently lists 77 packages found in most profiles (?). The |
15 |
'/usr/portage/profiles/arch.list' dir lists not only the recognized arches |
16 |
but also "Prefix Keywords". I'm not exactly sure how all of this profile |
17 |
stuff works; who decides what's (packages) in and out, package_masks etc etc. |
18 |
|
19 |
|
20 |
So my questions related to how does gentoo actually determines the exact |
21 |
list of programs that are minimally installed, with the specific |
22 |
arch and the profile selected? In previous times, I just put USE='-*' in the |
23 |
make.conf file and built upwards from there. Still there were baseline |
24 |
packages in the most minimal of stage based gentoo builds. I'm looking for a |
25 |
current approach to bridging between a baseline default profile (for amd64 |
26 |
that would be: [1] default/linux/amd64/13.0 *) and an embedded amd64 |
27 |
profile (if one currently exist? How do I find the potential profiles for |
28 |
say another arch (ppc for example), from an amd64 based gentoo system? |
29 |
Tools? Recommended scripts to review? |
30 |
|
31 |
|
32 |
'eselect profile list' currently shows 21 amd64 choices: |
33 |
|
34 |
[1] default/linux/amd64/13.0 * |
35 |
[2] default/linux/amd64/13.0/selinux |
36 |
[3] default/linux/amd64/13.0/desktop |
37 |
[4] default/linux/amd64/13.0/desktop/gnome |
38 |
[5] default/linux/amd64/13.0/desktop/gnome/systemd |
39 |
[6] default/linux/amd64/13.0/desktop/kde |
40 |
[7] default/linux/amd64/13.0/desktop/kde/systemd |
41 |
[8] default/linux/amd64/13.0/desktop/plasma |
42 |
[9] default/linux/amd64/13.0/desktop/plasma/systemd |
43 |
[10] default/linux/amd64/13.0/developer |
44 |
[11] default/linux/amd64/13.0/no-multilib |
45 |
[12] default/linux/amd64/13.0/systemd |
46 |
[13] default/linux/amd64/13.0/x32 |
47 |
[14] hardened/linux/amd64 |
48 |
[15] hardened/linux/amd64/selinux |
49 |
[16] hardened/linux/amd64/no-multilib |
50 |
[17] hardened/linux/amd64/no-multilib/selinux |
51 |
[18] hardened/linux/amd64/x32 |
52 |
[19] hardened/linux/musl/amd64 |
53 |
[20] default/linux/uclibc/amd64 |
54 |
[21] hardened/linux/uclibc/amd64 |
55 |
|
56 |
|
57 |
|
58 |
But looking here at the files and directories ( ls /usr/portage/profiles) |
59 |
|
60 |
I see an organization structure that differs from the profile listing |
61 |
semantics. So is there a script(s) that shows me what is being read from |
62 |
the directory tree that yields those 21 choices? It seems a bit convoluted |
63 |
to me, but I could easily have missed the documents that organize and |
64 |
discuss such details? Or at least a listing of the scripts that build these |
65 |
profile lists? Or is this adhoc? |
66 |
|
67 |
|
68 |
The next thought is how then to best (succinctly) determine the complete |
69 |
list of packages that will be pulled into any given (arch) profile. Is this |
70 |
a fiefdom situation where those devs that maintain that arch (tongue in |
71 |
cheek) quasi-use these scripts, config files and the /usr/portage/profiles |
72 |
tree structure, consistently or as they wish? I'm not looking for emotional |
73 |
responses, just clarity on where we are. |
74 |
|
75 |
Finally. What if I want to "roll my own profiles"; should I just build on |
76 |
one of the minimal ones or create something anew that exists only on my |
77 |
systems? If the latter, any insight or examples would be keen information. |
78 |
Yes, I know messing with the 'will of the dev(masters) will put me on a |
79 |
course of little help; but I just see a better way that I want to experiment |
80 |
with the profile pieces that are integral to my efforts. My main goal is to |
81 |
bridge the gap between what is embedded (truly minimalistic) |
82 |
and a minimized (via the profile) gentoo system. |
83 |
|
84 |
|
85 |
TIA, |
86 |
James |