1 |
Hello! |
2 |
|
3 |
|
4 |
This time my status update will take you closer to the land of details. |
5 |
A few things are not new, but many are; read on please. |
6 |
|
7 |
- Decisions that rbu and I have agreed on (in doubt mistakes are |
8 |
mine): |
9 |
|
10 |
- USE_EXPAND use flags (e.g. ALSA_CARDS) are now handled like |
11 |
normal use flags (e.g. ssl). They were stripped away until |
12 |
recently. |
13 |
|
14 |
- Overlay names from layman-global.txt are assumed to be globally |
15 |
unique and used for overlay identification. One of the |
16 |
consequences of that is that you we can collect data from global |
17 |
overlays (e.g. sunrise) that you do not manage with layman. |
18 |
|
19 |
- rsync excludes and filters from PORTAGE_RSYNC_EXTRA_OPTS will |
20 |
not be handled. It would be an inadequately complex extra task |
21 |
while not really gaining much at the same time. It would also |
22 |
require to write code at a level where we can currently use |
23 |
unmodified portage API. |
24 |
|
25 |
- package.use data will not be collected: We collect the set of |
26 |
actually used flags for each package installed and the set of |
27 |
global use flags already. The source of a use flag beyond that |
28 |
(i.e. distinct USE= in env versus and entry package.use) does |
29 |
not seem useful to us. |
30 |
|
31 |
- package.{keywords,unmask} and world file entries will not be |
32 |
collected separately but grouped with the list of installed |
33 |
packages as this data makes most sense together. For each |
34 |
package we are now collecting: |
35 |
|
36 |
- Category and package name |
37 |
- Version and revision |
38 |
- Slot |
39 |
- Keyword status |
40 |
i.e. what kind of package.keywords entry would be needed |
41 |
to re-install the package now. Can be one of: |
42 |
- '' means the package is no less stable than the |
43 |
system itself |
44 |
- '~arch' means an unstable package on a stable system |
45 |
- '**' catches case KEYWORDS='' mainly |
46 |
- Masked flag |
47 |
- Unmasked flag |
48 |
- In-world-file flag |
49 |
- Source overlay/tree name |
50 |
(e.g. 'gentoo' or 'sunrise') |
51 |
- Relevant enabled flags |
52 |
(subset of ISUE from the related ebuild) |
53 |
|
54 |
package.mask cannot be combined with installed package stats in |
55 |
all cases and will be reported separately as planned before. |
56 |
|
57 |
- Collection and auto-filtering of Gentoo-specific machine data is now |
58 |
complete: |
59 |
|
60 |
- Compile flags |
61 |
- CFLAGS, CXXFLAGS, LDFLAGS (right, that's link flags ...) |
62 |
- Basic GCC-oriented parsing |
63 |
|
64 |
- Global use flags |
65 |
- Parsing of profiles/... |
66 |
- arch.list |
67 |
- use.desc |
68 |
- use.local.desc |
69 |
- desc/*.desc |
70 |
- Filtering away other use flags |
71 |
|
72 |
- Installed packages |
73 |
- Filtering away packages that are not from the main tree or |
74 |
a layman-global overlay |
75 |
- More details given above |
76 |
|
77 |
- Make options |
78 |
- Basic GNU make-oriented parsing |
79 |
|
80 |
- Mirrors |
81 |
- Distfiles mirrors (filtered against synced copy of |
82 |
mirrors3.xml) |
83 |
- rsync mirror (filtered against gentoo.org host) |
84 |
|
85 |
- Overlays |
86 |
- Filtered against synced copy of layman-global.txt |
87 |
- Works without Layman installed |
88 |
|
89 |
- User package.mask |
90 |
- Filtering away packages that are not from the main tree or |
91 |
a layman-global overlay |
92 |
|
93 |
- System profile |
94 |
|
95 |
- Trivial portage scalars: |
96 |
- ARCH |
97 |
- CHOST |
98 |
- USE_ORDER |
99 |
|
100 |
- Trivial portage vectors: |
101 |
- ACCEPT_KEYWORDS |
102 |
- FEATURES |
103 |
|
104 |
- On my list of further data to collect at the moment: |
105 |
- Alpha CPU details |
106 |
(see mail "Project summaries - Alpha Arch Team") |
107 |
|
108 |
- All code over here [1], review welcome: |
109 |
|
110 |
|
111 |
Sebastian |
112 |
|
113 |
|
114 |
[1] |
115 |
http://git.goodpoint.de/?p=smolt-gentoo.git;a=tree;f=client/distros/gentoo;hb=refs/heads/gentoo |