Hi,

Ulrich Mueller <ulm@g.o>:
> >>>>> On Mon, 20 Dec 2010, Christian Faulhammer wrote:
> 
> > Should I merge all patches in one or feature by feature?
> 
> I would commit everything at once, but I think that's really up to
> you.

 Will probably do that to not pollute the trunk log.
 
> > Please review, they might have some rough edges still.
> 
> Thank you for all the work. See below for my comments.
> 
> >> \t{S} to \t{WORKDIR} fallback restricted
[...] 
> It more or less means "this is a virtual package".

 Ok, I read the exceptions but I was not sure how to do that shorter
(as it is minor stuff), but I will be a bit "incorrect" by saying
virtual.

> 
> > Subject: [PATCH 03/10] EAPI Cheat Sheet: Add PROPERTIES
> > [...]
> > +    \item[\code{PROPERTIES}] Is allowed for all package managers
> > now
> > +    to support interactive installs.
> 
> It's allowed already now (in all EAPIs), but in EAPI 4 support for
> PROPERTIES is mandatory.

 Fixed locally.  Will wait for other reviewers then post a new round.
 
> > Subject: [PATCH 07/10] EAPI Cheat Sheet: Describe MERGE_TYPE
> > variable
[...]
> This is a little long, but it's a matter of taste of course.

 Will see if I can do anything about it.
 
> > Subject: [PATCH 09/10] EAPI Cheat Sheet: Describe REQUIRED_USE and
> > pkg_required_use [...]
> > +    \item[\code{REQUIRED\_USE}] This variable can be used similar
> > to
> > +    the \code{(R|P)DEPEND} variables and define sets of USE flag
> > +    combinations that are not allowed.  All elements can be further
> > +    nested to achieve more functionality.
> > +    \begin{description}
> > +        \item[Forbidden combination] To prevent activation of
> > +        \code{flag1} if \code{flag2} is enabled use "\code{flag2? (
> > +            !flag1 )}".
> > +        \item[OR] If at least one USE flag out of many must be
> > +        activated on \code{flag1} use "\code{flag1? || ( flag2
> > flag3
> > +            \dots )}".
> > +        \item[XOR] To allow exactly one USE flag out of many use
> > +        "\code{\textasciicircum\textasciicircum ( flag1 flag2
> > \dots )}".
> > +    \end{description}
> > +    If those restrictions are violated by the user settings the
> > +    \code{pkg\_required\_use} function is run, where advise can be
> > +    given to the user how to set USE flags.  See
> > +    \featureref{required-use}.
> 
> The pkg_required_use function was rejected by the council, so the
> sentence immediately after the description list should be deleted.

 Ok.
 
> BTW, I had the same problem as above, that neither \t{^^} nor \t{\^\^}
> work in LaTeX. Does anybody know a shorter solution than
> \t{\textasciicircum\textasciicircum}?

 catcode redefinition...we do not want to do that.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>