1 |
Hi, |
2 |
|
3 |
Ulrich Mueller <ulm@g.o>: |
4 |
> >>>>> On Mon, 20 Dec 2010, Christian Faulhammer wrote: |
5 |
> |
6 |
> > Should I merge all patches in one or feature by feature? |
7 |
> |
8 |
> I would commit everything at once, but I think that's really up to |
9 |
> you. |
10 |
|
11 |
Will probably do that to not pollute the trunk log. |
12 |
|
13 |
> > Please review, they might have some rough edges still. |
14 |
> |
15 |
> Thank you for all the work. See below for my comments. |
16 |
> |
17 |
> >> \t{S} to \t{WORKDIR} fallback restricted |
18 |
[...] |
19 |
> It more or less means "this is a virtual package". |
20 |
|
21 |
Ok, I read the exceptions but I was not sure how to do that shorter |
22 |
(as it is minor stuff), but I will be a bit "incorrect" by saying |
23 |
virtual. |
24 |
|
25 |
> |
26 |
> > Subject: [PATCH 03/10] EAPI Cheat Sheet: Add PROPERTIES |
27 |
> > [...] |
28 |
> > + \item[\code{PROPERTIES}] Is allowed for all package managers |
29 |
> > now |
30 |
> > + to support interactive installs. |
31 |
> |
32 |
> It's allowed already now (in all EAPIs), but in EAPI 4 support for |
33 |
> PROPERTIES is mandatory. |
34 |
|
35 |
Fixed locally. Will wait for other reviewers then post a new round. |
36 |
|
37 |
> > Subject: [PATCH 07/10] EAPI Cheat Sheet: Describe MERGE_TYPE |
38 |
> > variable |
39 |
[...] |
40 |
> This is a little long, but it's a matter of taste of course. |
41 |
|
42 |
Will see if I can do anything about it. |
43 |
|
44 |
> > Subject: [PATCH 09/10] EAPI Cheat Sheet: Describe REQUIRED_USE and |
45 |
> > pkg_required_use [...] |
46 |
> > + \item[\code{REQUIRED\_USE}] This variable can be used similar |
47 |
> > to |
48 |
> > + the \code{(R|P)DEPEND} variables and define sets of USE flag |
49 |
> > + combinations that are not allowed. All elements can be further |
50 |
> > + nested to achieve more functionality. |
51 |
> > + \begin{description} |
52 |
> > + \item[Forbidden combination] To prevent activation of |
53 |
> > + \code{flag1} if \code{flag2} is enabled use "\code{flag2? ( |
54 |
> > + !flag1 )}". |
55 |
> > + \item[OR] If at least one USE flag out of many must be |
56 |
> > + activated on \code{flag1} use "\code{flag1? || ( flag2 |
57 |
> > flag3 |
58 |
> > + \dots )}". |
59 |
> > + \item[XOR] To allow exactly one USE flag out of many use |
60 |
> > + "\code{\textasciicircum\textasciicircum ( flag1 flag2 |
61 |
> > \dots )}". |
62 |
> > + \end{description} |
63 |
> > + If those restrictions are violated by the user settings the |
64 |
> > + \code{pkg\_required\_use} function is run, where advise can be |
65 |
> > + given to the user how to set USE flags. See |
66 |
> > + \featureref{required-use}. |
67 |
> |
68 |
> The pkg_required_use function was rejected by the council, so the |
69 |
> sentence immediately after the description list should be deleted. |
70 |
|
71 |
Ok. |
72 |
|
73 |
> BTW, I had the same problem as above, that neither \t{^^} nor \t{\^\^} |
74 |
> work in LaTeX. Does anybody know a shorter solution than |
75 |
> \t{\textasciicircum\textasciicircum}? |
76 |
|
77 |
catcode redefinition...we do not want to do that. |
78 |
|
79 |
V-Li |
80 |
|
81 |
-- |
82 |
Christian Faulhammer, Gentoo Lisp project |
83 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
84 |
|
85 |
<URL:http://gentoo.faulhammer.org/> |