When it says ``as if SYSROOT were simply /'', it means that if you write
ROOT="/" in the ${SYSROOT}/etc/make.conf file (maybe a variable like
PKGDIR), the variable will be postprocessed by portage to be
ROOT=${PORTAGE_CONFIGROOT}/${ROOT}, which is equal to
ROOT=${PORTAGE_CONFIGROOT}//, which is equal to
ROOT=${PORTAGE_CONFIGROOT}. Thus, if you are attempted to type out the
SYSROOT in the ${SYSROOT}/etc/make.conf file, you should replace it with
a simple `/', for portage will rewrite it.
So, if you were writing the ${SYSROOT}/etc/make.conf and wanted to set
the PKGDIR variable so that if you passed --buildpkg to emerge the
packages would show up in ${SYSROOT}/packages/, you would set the
variable in the file to PKGDIR=/packages. This allows consistency for,
if it was possible, you wanted to chroot into ${SYSROOT} or copy it onto
a machine that natively executes the files in it, the portage running
inside the chroot or new machine where the file is found in
/etc/make.conf doesn't have hardcoded in it, for example,
PKGDIR=/usr/i586-pc-linux-gnu/packages, but instead points to the same
directory, just found at the path of /packages.
I hope this clarifies the sentence - that's what I understand of it.
Your interpretation of the first sentence saying it should include
``*full* paths'' seems to indicate you'd type
PKGDIR=/usr/i586-pc-linux-gnu/packages rather than PKGDIR=/packages in
the example I attempted to give, while the sentence you are questioning
means, maybe not clearly, that you should replace the value of SYSROOT
in your mind with a simple `/' when editing the ${SYSROOT}/etc/make.conf
file. You are, as the sentence says, acting as if ${SYSROOT} were simply
"/".
Philippe Bertin wrote:
> Hello, all,
>
> On the page in subject, there's 2 sentences which are contradictory
> one another to my feeling. Either it's me, either this is a hint to
> eventually change the sentences :
> "Create a $SYSROOT/etc/make.conf file, and assign any path-related
> values in it as if SYSROOT were simply /. emerge should automatically
> adjust these values whenever ROOT and PORTAGE_CONFIGROOT are set to
> something other than /". Let's take, for an example's sake, a SYSROOT
> of "/usr/i586-pc-linux-gnu"
>
> The first sentence makes think that one should specify *full* paths.
> Because if one would need e.g. to specify a file
> /usr/i586-pc-linux-gnu/etc/make.conf, then one would specify ("as if
> SYSROOT were simply /") that file as
> "/usr/i586-pc-linux-gnu/etc/make.conf".
>
> On the other hand, I don't believe that's really the intention,
> because the second sentence kind of contradicts this: why would there
> be the need to specify full paths, if emerge automatically adjusts
> these values anyway ? So then I'd specify "/etc/make.conf", and have
> SYSROOT and emerge do their work.
>
> The example some lines further down the page doesn't come to the
> rescue either, as there aren't any path- related files specified in
> there. Is this one such of these opportunities for creating a better
> doc (and : what is the intention : specify full paths, or not) ?
>
> Kind regards
>
>
--
[EMAIL PROTECTED] mailing list
