1 |
Hi, |
2 |
|
3 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>: |
4 |
[chapters subdir] |
5 |
> Well, it's really an all or nothing thing. And all's going to be a |
6 |
> pain until we're sure we aren't going to have to go back and edit the |
7 |
> history. |
8 |
|
9 |
We can wait with it. |
10 |
|
11 |
|
12 |
> > 0001: Desk reference, updated and all issues you raised handled. |
13 |
> |
14 |
> You're indenting with two spaces rather than four, and don't have our |
15 |
> precious vim modelines. Lack of consistency makes me cry! |
16 |
|
17 |
Then go change the other files, and if Vim is too dumb to recognise a |
18 |
LaTeX file, I can't help it. |
19 |
|
20 |
> > + from the same checkout as this overview. |
21 |
> |
22 |
> has trailing whitespace. Git moans about this. |
23 |
|
24 |
Fixed. |
25 |
|
26 |
> > + Please report mistakes or enhancements to this document via the |
27 |
> |
28 |
> should read "mistakes in or enhancements to" |
29 |
> |
30 |
> > +Currently there is no full specification what EAPI 0 includes. |
31 |
> > +Portage, official ebuild documentation and existing ebuilds set the |
32 |
> > +standard here, although obvious errors are still errors. |
33 |
> |
34 |
> I'm wondering whether we can tone this (and the similar wording in |
35 |
> PMS) down a bit. The Council approved PMS as "correct, except where |
36 |
> people file bugs" a while back. |
37 |
> |
38 |
> > + disabled explicitely by user configuration) with a \code{+} sign |
39 |
> > in |
40 |
> |
41 |
> Spelling of 'explicitly'. |
42 |
> |
43 |
> > +\item[Named slot dependencies] Dependencies can explicitely |
44 |
> > request a |
45 |
> |
46 |
> Ditto. |
47 |
> |
48 |
> > +\item[\code{SRC\_URI} arrows] Allows redirection of upstream file |
49 |
> > + naming scheme by using an "arrow" (\code{->}) to a new file name |
50 |
> > in |
51 |
> > + DISTDIR. See \featureref{src-uri-arrows}. |
52 |
> |
53 |
> Not sure on this wording. How about something like: |
54 |
> |
55 |
> SRC_URI="http://some/url -> foo" can be used to use foo as the |
56 |
> filename for downloads. |
57 |
> |
58 |
> > +\item[USE dependencies] Dependencies can be specified to be built |
59 |
> > with |
60 |
> > + or without a specific USE flag, thus getting rid of countless |
61 |
> > + \code{built\_with\_use} checks. A more sophisticated syntax is |
62 |
> > + available in EAPI 3. |
63 |
> |
64 |
> Dependencies can specify use flag requirements on their target, |
65 |
> removing the need for built_with_use checks. A more powerful |
66 |
> syntax that does not require the flag to be in IUSE is in EAPI 3. |
67 |
> |
68 |
> > + Patching and other preparing tasks must no longer take place in |
69 |
> > + \code{src\_unpack} but in \code{src\_prepare}. |
70 |
> |
71 |
> Patching and similar preparation must now be done in src_prepare, |
72 |
> not src_unpack. |
73 |
> |
74 |
> > + be called via \code{default\_\emph{phasename}}, so small |
75 |
> > additions |
76 |
> > + you need will not be accompanied by a complete reimplementation |
77 |
> > of |
78 |
> > + the phase. Additionally as a shorthand for the current phase's |
79 |
> > + default definition \code{default} can be invoked. |
80 |
> |
81 |
> so duplicating the standard implementation is no longer necessary. |
82 |
> The default function calls the current phase's default_ function |
83 |
> automatically. |
84 |
> |
85 |
> > + Duplicating checks from the \code{pkg\_setup} phase may be |
86 |
> > + necessary. |
87 |
> |
88 |
> Most checks should usually be repeated in pkg_setup. |
89 |
> |
90 |
> > + phase can be called even for non-installed packages. Do not |
91 |
> > depend |
92 |
> > + on any outside programs in that case! See \featureref{pkg-info}. |
93 |
> |
94 |
> Be warned that dependencies might not have been installed. |
95 |
> |
96 |
> > +\item[Slot operators] There are two ways to define a wanted slot |
97 |
> > in a |
98 |
> > + dependency string: |
99 |
> |
100 |
> Dependencies that are both DEPEND and RDEPEND and that can match |
101 |
> multiple slots should specify one of: |
102 |
> |
103 |
> > +\item[USE dependency defaults] Additionally to the features |
104 |
> > offered in |
105 |
> |
106 |
> In addition to the ... |
107 |
> |
108 |
> > + after a USE flag (mind the braces). |
109 |
> |
110 |
> Braces are {}. You want brackets or parentheses. |
111 |
> |
112 |
> > The former leads to the |
113 |
> > + assumption that the USE flag is available when not found in the |
114 |
> > + dependency, the latter leads to the reverse behaviour. This |
115 |
> > mimicks |
116 |
> > + parts of the behaviour of \code{-{}-missing} in |
117 |
> |
118 |
> The former specifies that flags not in IUSE should be treated as |
119 |
> enabled; the latter, disabled. Cannot be used with USE_EXPAND |
120 |
> flags. |
121 |
> |
122 |
> > + \code{/usr/share\{doc,info,man\}} are compressed on-disk after |
123 |
> |
124 |
> s/are/may be |
125 |
> |
126 |
> > + With \code{docompress} all arguments are passed to the inclusion |
127 |
> > + list, while the behaviour can be inverted with the \code{-x} |
128 |
> > + switch. See \featureref{controllable-compress}. |
129 |
> |
130 |
> docompress path ... adds paths to the inclusion list for |
131 |
> compression. docompress -x path ... adds paths to the exclusion |
132 |
> list. |
133 |
> |
134 |
> > + files respectively in the known manner. |
135 |
> |
136 |
> "in the known manner" sounds weird. |
137 |
> |
138 |
> > + command given as argument will not abort the build process in |
139 |
> > case |
140 |
> > + of a failure but preserve the exit status nonetheless. See |
141 |
> |
142 |
> I'd mention that commands die on error before this. And then: |
143 |
> |
144 |
> will return non-zero on failure rather than aborting the build. |
145 |
> |
146 |
> > +\item[USE flags in any-of] Inside of \code{||} constructs USE flag |
147 |
> > + conditionals are forbidden (with exceptions). |
148 |
> |
149 |
> use? ( ) blocks are forbidden as direct children of || ( ) blocks. |
150 |
> |
151 |
> > + anymore. |
152 |
> |
153 |
> 'anymore' as a single word is generally considered horrible. |
154 |
|
155 |
Adressed I hope. Last iteration, what you don't find now, will go in |
156 |
later. |
157 |
|
158 |
And more patches: |
159 |
0001: Corrected desk reference. |
160 |
0002: Tell Emacs to use retarded indenting in all LaTeX files, so the |
161 |
Vim weenies don't whine. |
162 |
0003: Fix intendation to 4 spaces where needed. |
163 |
0004: Comment class file |
164 |
0005: Kick out appendix.sty and a little appendix tweak |
165 |
0006: Some minor Makefile tweaking |
166 |
0007: Make email addresses clickable |
167 |
|
168 |
And for inital review: |
169 |
0008: Add Gentoo logo to PMS and desk reference. |
170 |
|
171 |
V-Li |
172 |
|
173 |
-- |
174 |
Christian Faulhammer, Gentoo Lisp project |
175 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
176 |
|
177 |
<URL:http://gentoo.faulhammer.org/> |