Gentoo Archives: gentoo-dev

From: Denis Dupeyron <calchan@g.o>
To: gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds
Date: Wed, 25 Nov 2009 23:44:31
Message-Id: 7c612fc60911251543p70dfa240gf09feb46f18e3323@mail.gmail.com
In Reply to: Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds by Fabian Groffen
1 Things seem to be progressing nicely on this front. We have answers to
2 the questions people had and they look satisfactory to me.
3
4 One thing that I think would be valuable is a document that explains
5 the average dev how to make his/her ebuilds prefix compliant with
6 links to more details when necessary. I understand that there's the
7 trivial situations and the less trivial ones. In the latter case it
8 would be nice to explain why the case isn't trivial and how to fix it.
9 Using python as an example could be one way to do it. I'm thinking of
10 something practical that could possibly be patched into devmanual. If
11 such a document already exists then please just point us to it.
12
13 On Fri, Nov 20, 2009 at 2:03 AM, Fabian Groffen <grobian@g.o> wrote:
14 >> I thought I asked Fabian to work on that at the end of the meeting. In
15 >> case I didn't then consider this as me officially asking him if he can
16 >> take care of it. Fabian is this OK with you?
17 >
18 > Yes, I agreed coming up with some patch.  I admit I haven't yet even
19 > looked into it.
20
21 Great, thanks. If you can have it ready some time before the meeting
22 so that all devs can get a chance to review it before the council
23 members vote on it that will be even better. If you need help don't
24 hesitate to contact me. I'll try and look for the right people to help
25 you depending on what you need.
26
27 > Technically, Portage trunk already contains the most important bits that
28 > allow us to continue since yesterday.  The rest is waiting for a formal
29 > approval of the council, and then it will most probably be me and Zac
30 > fighting to get the prefix branch merged into trunk.
31
32 Good.
33
34 > Next to that, it is part of the Prefix team's job to make sure that
35 > whatever is installed, does not reference the host system when this is
36 > not absolutely necessary.
37
38 Could you give some examples of when it is absolutely necessary?
39
40 Denis.

Replies