From: "Aaron W. Swenson" <titanofold@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Cleaning up PMS to have ${D} not end with a slash
Date: Mon, 15 Apr 2013 10:56:45 +0000 [thread overview]
Message-ID: <20130415105644.GA5854@gengoff.local.grandmasfridge.org> (raw)
In-Reply-To: <20130414185919.5c9d8632@pomiocik.lan>
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
On Sun, Apr 14, 2013 at 06:59:19PM +0200, Michał Górny wrote:
> On Sun, 14 Apr 2013 17:39:44 +0100
> Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
>
> > On Sun, 14 Apr 2013 16:58:07 +0200
> > Michał Górny <mgorny@gentoo.org> wrote:
> > > On Sun, 14 Apr 2013 15:22:42 +0100
> > > Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> > > > On Sat, 13 Apr 2013 23:23:57 +0200
> > > > Michał Górny <mgorny@gentoo.org> wrote:
> > > > Should ROOT usually be empty then?
> > >
> > > Considering its use, probably yes.
> > >
> > > ${ROOT}/usr/bin/foo
> > > ${EPREFIX}/usr/bin/foo
> > > ${D}${EPREFIX}/usr/bin/foo
> > >
> > > All seem clean and consistent to me.
> >
> > How many things test whether ROOT=/ ? I seem to recall that being
> > fairly common, back when something accidentally set it to //.
>
> Yes, that sucks a fair bit. There are many ebuilds doing that, and most
> of those ebuilds append additional slash after it anyway... we really
> suck at consistency.
>
We're only accountable insofar as ROOT defaults to "/".
ROOT being a user set variable, having ROOT be an empty string by
default still does not guarantee that ROOT won't end with a
slash. Even if we change it so that it defaults to an empty string, it
won't negate the need to do ${ROOT%/}/some/path.
The only thing that would help is if PMS defined that ROOT must not
end with a slash. In which case it would be up to the package manage
to modify ROOT before it gets evaluated in an ebuild.
--
Mr. Aaron W. Swenson
Gentoo Linux Developer
Email : titanofold@gentoo.org
GnuPG FP : 2C00 7719 4F85 FB07 A49C 0E31 5713 AA03 D1BB FDA0
GnuPG ID : D1BBFDA0
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2013-04-15 10:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 21:23 [gentoo-dev] [RFC] Cleaning up PMS to have ${D} not end with a slash Michał Górny
2013-04-14 8:31 ` Gregory M. Turner
2013-04-14 10:24 ` Peter Stuge
2013-04-14 11:32 ` Michał Górny
2013-04-14 11:34 ` Michał Górny
2013-04-14 14:14 ` hasufell
2013-04-14 15:01 ` Michał Górny
2013-04-14 14:22 ` Ciaran McCreesh
2013-04-14 14:58 ` Michał Górny
2013-04-14 16:39 ` Ciaran McCreesh
2013-04-14 16:59 ` Michał Górny
2013-04-15 10:56 ` Aaron W. Swenson [this message]
2013-04-15 11:01 ` Ciaran McCreesh
2013-04-15 17:31 ` [gentoo-dev] " Steven J. Long
2013-04-15 18:54 ` Gregory M. Turner
2013-04-18 23:02 ` [gentoo-dev] " Steven J. Long
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=20130415105644.GA5854@gengoff.local.grandmasfridge.org \
--to=titanofold@gentoo.org \
--cc=gentoo-dev@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