Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Fabian Groffen <grobian@g.o>
Subject: Re: Re: [RFC] Font eclass EAPI update and design
Date: Tue, 2 Feb 2010 11:50:04 +0100
On 02-02-2010 11:18:32 +0100, Torsten Veller wrote:
> > 	# Prefix compat
> > 	case ${EAPI:-0} in
> > 		0|1|2)
> > 			if ! use prefix; then
> > 				EPREFIX=
> > 				ED=${D}
> > 				EROOT=${ROOT}
> > 				[[ ${EROOT} = */ ]] || EROOT+="/"
> > 			fi
> > 			;;
> > 	esac
> 
> Don't we need this for every eclass using EPREFIX, ED and EROOT
> independent of EAPI?
> Can't we move this to prefix.eclass and inherit it? Or is the EPREFIX
> setting in prefix.eclass already enough?

You cannot set EROOT and ED (reliably) from prefix.eclass, unless you
wrap them in phase funcs for which ROOT and D are guaranteed to be
defined.  OIW: The logic can be moved but a simple "inherit prefix"
won't be enough to use EROOT and ED.


-- 
Fabian Groffen
Gentoo on a different level


References:
[RFC] Font eclass EAPI update and design
-- Tomáš Chvátal
Re: [RFC] Font eclass EAPI update and design
-- Torsten Veller
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: [RFC] Font eclass EAPI update and design
Next by thread:
Recent lists mail loss
Previous by date:
Re: Re: [RFC] Font eclass EAPI update and design
Next by date:
an update script for the gentoo developer


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.