public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds
Date: Thu, 26 Nov 2009 10:01:24 +0000 (UTC)	[thread overview]
Message-ID: <pan.2009.11.26.10.01.23@cox.net> (raw)
In-Reply-To: 20091126085303.GG19586@gentoo.org

Fabian Groffen posted on Thu, 26 Nov 2009 09:53:04 +0100 as excerpted:

>> > Next to that, it is part of the Prefix team's job to make sure that
>> > whatever is installed, does not reference the host system when this
>> > is not absolutely necessary.
>> 
>> Could you give some examples of when it is absolutely necessary?
> 
> Simple example is perl.  If you install a script, for instance ekeyword,
> then it is important that this script doesn't say '#!/usr/bin/perl' in
> its shebang.  "/usr/bin/perl" may simply not exist, but more importantly
> it is not the perl that Portage has installed and also installed all
> required dependencies for.  Hence, ekeyword should be installed such
> that it references the perl from the offset installation, e.g.
> "/home/joe/gentoo/usr/bin/perl".
> 
> "/bin/sh" is another nice one.

At least here, that it would ordinarily be best to reference the prefix 
system was taken for granted, so when it's "absolutely necessary" to 
reference the host system is the interesting case, and how I parsed the 
request.  You provided examples of just the opposite, the case I (and 
evidently Denis, if I parsed the request correctly) assumed to be normal, 
where referencing the prefix is strongly desirable or "absolutely 
necessary".

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2009-11-26 10:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18  9:11 [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds Fabian Groffen
2009-10-18 11:57 ` Tomáš Chvátal
2009-10-18 12:31   ` Fabian Groffen
2009-10-19 19:44     ` Fabian Groffen
2009-10-24 19:37       ` Petteri Räty
2009-10-24 20:00         ` Fabian Groffen
2009-11-13 11:43       ` Ulrich Mueller
2009-11-20  8:45         ` Fabian Groffen
2009-11-20  0:26 ` Denis Dupeyron
2009-11-20  1:42   ` Jeremy Olexa
2009-11-20  9:03     ` Fabian Groffen
2009-11-25 23:43       ` Denis Dupeyron
2009-11-26  8:53         ` Fabian Groffen
2009-11-26 10:01           ` Duncan [this message]
2009-11-26 10:10             ` [gentoo-dev] " Fabian Groffen
2009-11-26 10:37               ` Duncan
2009-11-26 10:51                 ` Fabian Groffen
2009-11-26 12:36                   ` Duncan
2009-11-26 15:26                     ` Fabian Groffen
2009-11-26 13:43         ` [gentoo-dev] " Fabian Groffen
2009-11-26  0:01   ` Denis Dupeyron
2009-11-26  9:02     ` Fabian Groffen

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=pan.2009.11.26.10.01.23@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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