On 01/04/2011 10:22 AM, Ciaran McCreesh wrote: > On Mon, 03 Jan 2011 16:40:57 +0200 > Samuli Suominen <[email protected]> wrote: >> Far as I know, S= isn't used to generate metadata cache, so it's PMS >> that need fixing for it's wording: >> >> "All ebuild-defined variables used to generate metadata cache, >> discussed in this chapter..." > > There's also: > > Global variables must only contain invariant values > (see~\ref{sec:metadata-invariance}). If a global variable's value is > invariant, it may have the value that would be generated at any > given point in the build sequence. > > which is true for all global variables, not just for metadata ones. > That paragraph's there because historically global variables have done > various different things (being re-evaluated for every phase, or just > some phases, or never, or when loaded from VDB, or ...). >
I don't know the code involving package managers here, but we have eclasses like qt4-r2.eclass and kde4-meta.eclass redefining S= from src_unpack() and I haven't seen a single bug report about it. To fix the eclasses, and several ebuilds in tree to not do this for something that "might be a problem" or fix the PMS wording to match reality?
