Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-26 Thread Fabian Groffen
On 25-11-2009 16:43:32 -0700, Denis Dupeyron wrote: > > Yes, I agreed coming up with some patch.  I 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 vo

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-26 Thread Fabian Groffen
On 25-11-2009 17:01:19 -0700, Denis Dupeyron wrote: > It looks like this question is still unanswered: > > On Thu, Nov 19, 2009 at 5:26 PM, Denis Dupeyron wrote: > >> How are dynamically linked set*id programs going to work? Depends on how the host OS/libc handles this :) If you're root, you ca

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-26 Thread Fabian Groffen
On 25-11-2009 16:43:32 -0700, Denis Dupeyron wrote: > 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 e

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-25 Thread Denis Dupeyron
It looks like this question is still unanswered: On Thu, Nov 19, 2009 at 5:26 PM, Denis Dupeyron wrote: >> How are dynamically linked set*id programs going to work? Denis.

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-25 Thread Denis Dupeyron
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 necess

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-20 Thread Fabian Groffen
On 19-11-2009 19:42:11 -0600, Jeremy Olexa wrote: > Some questions answered. snipped the rest. readded questions where necessary > Denis Dupeyron wrote: > > 2009/10/18 Tomáš Chvátal : > >> Why on earth portage simply does not detect the prefix enviroment is being > >> run > >> and then INTERNALY

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-20 Thread Fabian Groffen
On 13-11-2009 12:43:25 +0100, Ulrich Mueller wrote: > In its November meeting [1], the council has unanimously expressed > support for this proposal [2]. > > However, there is need for additional discussion. From the council > meeting log I could extract the following open questions: > > 1. Wha

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-19 Thread Jeremy Olexa
Some questions answered. snipped the rest. Denis Dupeyron wrote: 2009/10/18 Tomáš Chvátal : Why on earth portage simply does not detect the prefix enviroment is being run and then INTERNALY switch D->ED and other variables. If that means we can get away without touching ebuilds, apart from ch

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-19 Thread Denis Dupeyron
On Sun, Oct 18, 2009 at 2:11 AM, Fabian Groffen wrote: > This is a formal apology for springing that onto you. Thanks a lot. Not everybody can do such a thing as a public apology. I will nonetheless ask the council to vote on the following during next meeting: Ask Fabian to change his signatu

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-11-13 Thread Ulrich Mueller
In its November meeting [1], the council has unanimously expressed support for this proposal [2]. However, there is need for additional discussion. From the council meeting log I could extract the following open questions: 1. What are the implications for non-prefix devs and users? 2. Shoul

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-10-24 Thread Fabian Groffen
On 24-10-2009 22:37:30 +0300, Petteri Räty wrote: > > The suggestion was to just introduce EAPI=3 with these variables, and > > making everything which is scheduled for current EAPI=3 just EAPI=4. I > > was told we could quite quickly have a Portage in the tree that would > > set ED and EROOT for

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-10-24 Thread Petteri Räty
Fabian Groffen wrote: > On 18-10-2009 14:31:15 +0200, Fabian Groffen wrote: >> On 18-10-2009 13:57:10 +0200, Tomáš Chvátal wrote: >>> Hi, >>> You know i am totaly supporting prefix but i have one point. >>> Why on earth portage simply does not detect the prefix enviroment is being >>> run >>> and

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-10-19 Thread Fabian Groffen
On 18-10-2009 14:31:15 +0200, Fabian Groffen wrote: > On 18-10-2009 13:57:10 +0200, Tomáš Chvátal wrote: > > Hi, > > You know i am totaly supporting prefix but i have one point. > > Why on earth portage simply does not detect the prefix enviroment is being > > run > > and then INTERNALY switch D-

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-10-18 Thread Fabian Groffen
On 18-10-2009 13:57:10 +0200, Tomáš Chvátal wrote: > Hi, > You know i am totaly supporting prefix but i have one point. > Why on earth portage simply does not detect the prefix enviroment is being > run > and then INTERNALY switch D->ED and other variables. It would be much easier > that way to

Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-10-18 Thread Tomáš Chvátal
Hi, You know i am totaly supporting prefix but i have one point. Why on earth portage simply does not detect the prefix enviroment is being run and then INTERNALY switch D->ED and other variables. It would be much easier that way to migrate all stuff in portage instead of doing this || shebang.

[gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds

2009-10-18 Thread Fabian Groffen
Recently, Prefix changes have been committed to the gentoo-x86 tree, it was rather ambitious on my part, where I moved stuff that we are not maintainer of ourself. It should have been communicated better for these ebuilds. This is a formal apology for springing that onto you. This will attempt to