From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable
Date: Wed, 12 Jun 2019 23:05:48 +0100 [thread overview]
Message-ID: <20190612230548.54091fea@symphony.aura-online.co.uk> (raw)
In-Reply-To: <w6g4l589nos.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Sun, 02 Jun 2019 14:28:03 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> That's a fundamental change of the variable's definition, so presumably
> it should be done in EAPI 8, not retroactively?
I would say no because the original definition simply doesn't make
sense and there's no point in perpetuating something that doesn't make
sense.
There has also been very little usage of ESYSROOT so far. Practically
all of it has been my own and all of it still fits with the new
definition.
> Also (though not really relevant at this point yet):
>
> (./dependencies.tex
> Chapter 8.
> Overfull \hbox (282.82272pt too wide) in paragraph at lines 33--44
Sorry, I didn't want to build TeX Live just for this. I'll do it now so
I can work this out.
--
James Le Cuirot (chewi)
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-12 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 22:29 [gentoo-pms] [PATCH] Correct the definition of ESYSROOT as EPREFIX isn't always applicable James Le Cuirot
2019-06-02 6:10 ` Michał Górny
2019-06-12 22:05 ` James Le Cuirot
2019-06-02 12:28 ` Ulrich Mueller
2019-06-12 22:05 ` James Le Cuirot [this message]
2019-06-14 7:07 ` Ulrich Mueller
2019-06-13 20:09 ` James Le Cuirot
2019-06-13 22:17 ` Ulrich Mueller
2019-06-14 22:23 ` James Le Cuirot
2019-06-14 22:30 ` James Le Cuirot
2019-06-15 8:18 ` Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190612230548.54091fea@symphony.aura-online.co.uk \
--to=chewi@gentoo.org \
--cc=gentoo-pms@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox