From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-38568-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1NDRXC-0001Xo-PZ
for garchives@archives.gentoo.org; Wed, 25 Nov 2009 23:44:31 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id B42F8E0A02;
Wed, 25 Nov 2009 23:43:41 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id 741BDE0A02
for <gentoo-dev@lists.gentoo.org>; Wed, 25 Nov 2009 23:43:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp.gentoo.org (Postfix) with ESMTP id 1377767CB5
for <gentoo-dev@lists.gentoo.org>; Wed, 25 Nov 2009 23:43:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at gentoo.org
X-Spam-Score: -1.972
X-Spam-Level:
X-Spam-Status: No, score=-1.972 required=5.5 tests=[AWL=0.627,
BAYES_00=-2.599]
Received: from smtp.gentoo.org ([127.0.0.1])
by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 2PxrEF+DpxFi for <gentoo-dev@lists.gentoo.org>;
Wed, 25 Nov 2009 23:43:34 +0000 (UTC)
Received: from mail-ew0-f223.google.com (mail-ew0-f223.google.com [209.85.219.223])
by smtp.gentoo.org (Postfix) with ESMTP id AEDA567CB1
for <gentoo-dev@gentoo.org>; Wed, 25 Nov 2009 23:43:33 +0000 (UTC)
Received: by ewy23 with SMTP id 23so268762ewy.24
for <gentoo-dev@gentoo.org>; Wed, 25 Nov 2009 15:43:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:received:in-reply-to
:references:date:x-google-sender-auth:message-id:subject:from:to
:content-type:content-transfer-encoding;
bh=PHOCeunKUTrZwcer3o3BdRAoP+ky1cD7qZ2FIIL4bEQ=;
b=XLLMAOUvL71yzdHyCMC74dxVfqv5ZztM4ZH7gvk9wM9uqY5e8cxIFTsrsPyn1kdOUA
fSicx3ufEQujSQG/i2IOvDoVaXUmpmKGi9ZKwCmAjgpYcVCb3hFdkkIflcP+kBomVP1M
l83FWt9EOxJPLCXL8fizeGds3iftD/wSHesg0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type
:content-transfer-encoding;
b=TaalIwcArqCDNKENTSbcjZPAzI/Dld5nwCN+IgtEONr9Po8DqDwt5tVNcL8mD9OpKo
UorVVtkoltmM7rpTDxXD9aBJgh6i4pBn0ftigS5mixQbJotsXKX7iE6e2ekLVwLTpV9v
MFQ53iyEFaTrvwohCiKgiqbcLO2OT8aLMeA2w=
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Sender: denis.dupeyron@gmail.com
Received: by 10.216.88.139 with SMTP id a11mr604830wef.50.1259192612653; Wed,
25 Nov 2009 15:43:32 -0800 (PST)
In-Reply-To: <20091120090338.GK19586@gentoo.org>
References: <20091018091154.GB464@gentoo.org>
<7c612fc60911191626p7c32374fhf597787f2d30dfd3@mail.gmail.com>
<4B05F3F3.9020902@gentoo.org> <20091120090338.GK19586@gentoo.org>
Date: Wed, 25 Nov 2009 16:43:32 -0700
X-Google-Sender-Auth: d11a49a2b718aaaa
Message-ID: <7c612fc60911251543p70dfa240gf09feb46f18e3323@mail.gmail.com>
Subject: Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside
ebuilds
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 6187af1a-9252-4099-aeed-4855fc901c4d
X-Archives-Hash: 849eb668fefe18bfae472f522c70812a
Things seem to be progressing nicely on this front. We have answers to
the questions people had and they look satisfactory to me.
One thing that I think would be valuable is a document that explains
the average dev how to make his/her ebuilds prefix compliant with
links to more details when necessary. I understand that there's the
trivial situations and the less trivial ones. In the latter case it
would be nice to explain why the case isn't trivial and how to fix it.
Using python as an example could be one way to do it. I'm thinking of
something practical that could possibly be patched into devmanual. If
such a document already exists then please just point us to it.
On Fri, Nov 20, 2009 at 2:03 AM, Fabian Groffen <grobian@gentoo.org> wrote:
>> I thought I asked Fabian to work on that at the end of the meeting. In
>> case I didn't then consider this as me officially asking him if he can
>> take care of it. Fabian is this OK with you?
>
> Yes, I agreed coming up with some patch. =A0I admit I haven't yet even
> looked into it.
Great, thanks. If you can have it ready some time before the meeting
so that all devs can get a chance to review it before the council
members vote on it that will be even better. If you need help don't
hesitate to contact me. I'll try and look for the right people to help
you depending on what you need.
> Technically, Portage trunk already contains the most important bits that
> allow us to continue since yesterday. =A0The rest is waiting for a formal
> approval of the council, and then it will most probably be me and Zac
> fighting to get the prefix branch merged into trunk.
Good.
> 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?
Denis.