1 |
On 08/13/18 11:47, james wrote: |
2 |
> On 08/13/18 11:36, Corentin �Nado� Pazdera wrote: |
3 |
>> August 13, 2018 4:31 PM, "james" <garftd@×××××××.net> wrote: |
4 |
>> |
5 |
>>> Any hints on a systematic by system parsing this sort of minimized-flag |
6 |
>>> data : |
7 |
>>> |
8 |
>>> [12] default/linux/amd64/17.0 (stable) * |
9 |
>>> |
10 |
>>> would be keenly appreciated. "eselect profile list" is great. but |
11 |
>>> I need it per many different architectures and do not have one |
12 |
>>> of each of the systems I need to experiment on. How are those flag_sets |
13 |
>>> discovered in some sort of systematic approach? |
14 |
>> |
15 |
>> Hi, |
16 |
>> |
17 |
>> I don't know if this will be of any help but I made a script [1] recently to analyze the |
18 |
>> inheritance of system set. |
19 |
>> It may have a few bugs I did that for learning the inner workings of profiles mainly. |
20 |
>> It should'nt need much work to make it print USE flags details |
21 |
>> |
22 |
>> [1] https://gist.github.com/nado/44b392b50c0b71a7e22b98d6909bfa72 |
23 |
>> |
24 |
>> Best regards, |
25 |
>> -- |
26 |
>> Corentin �Nado� Pazdera |
27 |
>> |
28 |
>> |
29 |
> |
30 |
> |
31 |
> Hey thanks, |
32 |
> |
33 |
> I'm testing now an it has given me a few ideas to extend the |
34 |
> capabilities.... |
35 |
> |
36 |
> |
37 |
> James |
38 |
> |
39 |
|
40 |
Here's what I got running your script:: |
41 |
|
42 |
|
43 |
/etc # /root/profile-explorer.sh |
44 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
45 |
/usr/portage/profiles/base/packages |
46 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
47 |
*>=sys-apps/baselayout-2 |
48 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
49 |
*>=sys-apps/findutils-4.4 |
50 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
51 |
*>=sys-devel/patch-2.7 |
52 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
53 |
/usr/portage/profiles/default/linux/packages |
54 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
55 |
/usr/portage/profiles/base/packages |
56 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
57 |
*>=sys-apps/baselayout-2 |
58 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
59 |
*>=sys-apps/findutils-4.4 |
60 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
61 |
*>=sys-devel/patch-2.7 |
62 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
63 |
/usr/portage/profiles/default/linux/packages |
64 |
|
65 |
|
66 |
Manually looking a the |
67 |
|
68 |
less /etc/portage/package.use/explored-packages: |
69 |
/usr/portage/profiles/base/packages |
70 |
|
71 |
|
72 |
I see: |
73 |
# Old ICU is unsupported. ICU 58 only remains for 13.0 based profiles. |
74 |
<dev-libs/icu-59 |
75 |
<dev-libs/icu-layoutex-59 |
76 |
|
77 |
But the system has:: |
78 |
|
79 |
[I] dev-libs/icu .... 60.2 |
80 |
|
81 |
equery uses icu |
82 |
|
83 |
gives me similar info: |
84 |
|
85 |
|
86 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
87 |
/usr/portage/profiles/base/packages |
88 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
89 |
*>=sys-apps/baselayout-2 |
90 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
91 |
*>=sys-apps/findutils-4.4 |
92 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
93 |
*>=sys-devel/patch-2.7 |
94 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
95 |
/usr/portage/profiles/default/linux/packages |
96 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
97 |
/usr/portage/profiles/base/packages |
98 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
99 |
*>=sys-apps/baselayout-2 |
100 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
101 |
*>=sys-apps/findutils-4.4 |
102 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
103 |
*>=sys-devel/patch-2.7 |
104 |
--- Invalid atom in /etc/portage/package.use/explored-packages: |
105 |
/usr/portage/profiles/default/linux/packages |
106 |
[ Legend : U - final flag setting for installation] |
107 |
[ : I - package is installed with flag ] |
108 |
[ Colors : set, unset ] |
109 |
* Found these USE flags for dev-libs/icu-60.2: |
110 |
U I |
111 |
+ + abi_x86_32 : 32-bit (x86) libraries |
112 |
- - debug : Enable extra debug codepaths, like asserts and extra |
113 |
output. If |
114 |
you want to get meaningful backtraces see |
115 |
|
116 |
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces |
117 |
- - doc : Add extra documentation (API, Javadoc, etc). It is |
118 |
recommended to |
119 |
enable per package instead of globally |
120 |
+ + examples : Install examples, usually source code |
121 |
- - static-libs : Build static versions of dynamic libraries as well |
122 |
|
123 |
|
124 |
|
125 |
|
126 |
Which begs the Q1} can I get rid of the flag icu? What are |
127 |
consequences, as a baseline system flag, of it's removal ? |
128 |
|
129 |
|
130 |
less /usr/portage/profiles/base/packages |
131 |
show me more of what the @system set contains. Very interesting and |
132 |
useful. I'm thinking of aggregation of those listed packages |
133 |
and some basic (ascii) table form (equery,emerge, eix) parsed listing |
134 |
of the default and current flag settings. A "verification" tool |
135 |
if you like. Surely it would help if this info was (is?) more readily |
136 |
available and organized for folks that need a systematic approach, like |
137 |
heterogeneous HPC clusters. The tools exist for 'ad-hoc' and one off, |
138 |
but more of an organized representation at least at the set level. |
139 |
|
140 |
I feel like there is an existing tool that can yield all of this |
141 |
information, as it is on a current system. I've read where there are |
142 |
efforts to clean up the packages and default flags used in @system, |
143 |
so the bare minimum list per arch/profiles would ultimately be |
144 |
a useful listing, particular for my HPC. In HPC less is always faster |
145 |
and better, as it is in security and so many more aspects of CS. |
146 |
|
147 |
|
148 |
Obviosly, I have a few things to fix on this (fragile) system, but |
149 |
that'll happen as I'm at the beginning stages of auto_installs of |
150 |
minimized systems. What are your plans for you little script? |
151 |
|
152 |
Just to match equery uses <flag> and such? |
153 |
|
154 |
|
155 |
Here's a cutie: |
156 |
/usr/portage/profiles/default/linux/amd64/package.use.mask |
157 |
|
158 |
# Mike Frysinger <vapier@g.o> (08 May 2016) |
159 |
# This target supports VTV #547040. |
160 |
>=sys-devel/gcc-4.9 -vtv |
161 |
|
162 |
# Mike Frysinger <vapier@g.o> (21 Oct 2014) |
163 |
# This target supports ASAN/etc... #504200. |
164 |
sys-devel/gcc -sanitize |
165 |
|
166 |
|
167 |
And where was it that the processor/arch flags are now listed? |
168 |
|
169 |
|
170 |
tia, |
171 |
James |
172 |
cat |