public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds
Date: Thu, 26 Nov 2009 16:26:09 +0100	[thread overview]
Message-ID: <20091126152609.GR19586@gentoo.org> (raw)
In-Reply-To: <pan.2009.11.26.12.36.38@cox.net>

On 26-11-2009 12:36:47 +0000, Duncan wrote:
> > I think there's unfortunately no simple way to tell what should be in
> > and what unfortunately has to be out.  It depends a lot on the host
> > system.  I feel -- but I can't back this up with hard evidence -- that
> > it are usually the libs that are not in *DEPEND that can only be
> > available in the host system.  Basically because they usually are part
> > of the libc, which we assume to be installed.
> > 
> > 
> > [1] http://dev.gentoo.org/~grobian/prefix-quiz
> 
> Thanks again.  That quiz was particularly enlightening (to this gentoo, 
> not prefix, user) on the type of stuff you think about, as a part of what 
> prefix /does/.

The following bug is a classical example of something which just happens
to work by accident, but is broken.  It also illustrates what kind of
changes people can expect to have to be made to their ebuilds to get
them to work for Prefix:

  http://bugs.gentoo.org/show_bug.cgi?id=293901

Because the ebuild gives a direct pointer to a place in the filesystem,

  --with-apr=/usr/bin/apr-1-config

the ebuild needs a change such that it points to the corresponding place
in the offset-prefix installation, e.g. under "${EPREFIX}".

  --with-apr="${EPREFIX}"/usr/bin/apr-1-config

When this variable is empty, there's obviously no change to the
behaviour of the ebuild.


-- 
Fabian Groffen
Gentoo on a different level



  reply	other threads:[~2009-11-26 15:26 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           ` [gentoo-dev] " Duncan
2009-11-26 10:10             ` 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 [this message]
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=20091126152609.GR19586@gentoo.org \
    --to=grobian@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