EPREFIX env ignored by portage

I was trying to create a
"prefix-portage-installer" dmg and ran into  
the following problem.
When portage is installed in the tarball, it's not possible
to get it  
to install in a different EPREFIX then the one it was
compiled with.

Example:

$ EPREFIX=/bla emerge --info
Portage 2.1.20.5894 (default-darwin/macos/10.4/x86,
gcc-4.0.1,  
unavailable, 8.8.1 i386)
============================================================
=====
System uname: 8.8.1 i386 i386
Gentoo Prefix Base System version 1.12.5

...
EPREFIX=/Volumes/GentooPrefix/
...

Even defining it in etc/make.conf doesn't seem to help.
Is this a bug or am I doing something wrong here...

When I get this fixed, we will have a very easy to use
bootstrap dmg  
which you can mount and then run emerge -e system to install
in EPREFIX.

Frank
-- 
gentoo-altgentoo.org mailing list

On 09-02-2007 23:03:50 +0100, Frank Groeneveld wrote:
> I was trying to create a
"prefix-portage-installer" dmg and ran into  
> the following problem.
> When portage is installed in the tarball, it's not
possible to get it  
> to install in a different EPREFIX then the one it was
compiled with.

Duh.

> Example:
> 
> $ EPREFIX=/bla emerge --info
> Portage 2.1.20.5894 (default-darwin/macos/10.4/x86,
gcc-4.0.1,  
> unavailable, 8.8.1 i386)
>
============================================================
=====
> System uname: 8.8.1 i386 i386
> Gentoo Prefix Base System version 1.12.5
> 
> ...
> EPREFIX=/Volumes/GentooPrefix/
> ...
> 
> Even defining it in etc/make.conf doesn't seem to
help.
> Is this a bug or am I doing something wrong here...

EPREFIX is a variable that is never set or overridden.  You
would simply
screw up your install if you would do, as portage would get
clueless as
to where to find what.

> When I get this fixed, we will have a very easy to use
bootstrap dmg  
> which you can mount and then run emerge -e system to
install in EPREFIX.

Well, I don't see a nice way out, and instead, I just would
suggest you
to set your path to include the dmg, and then bootstrap
portage.  The
configure stuff of portage allows you to split install and
eprefix
paths, but imho that only complicates matters.

-- 
Fabian Groffen
Gentoo on a different level

-- 
gentoo-altgentoo.org mailing list

I know how this works, but this is not the way grobian and
genstef  
want to create an "installer".
They want to provide a .dmg that contains the necessary
tools to run  
an emerge -e system to a specific location.
So you can download the dmg, mount it, set some env
variables and  
then start installing prefix-portage in, for example
/Library/Gentoo.

Frank

Op 10-feb-2007, om 2:15 heeft Tobias Hahn het volgende
geschreven:

> Actually, the solution is quite easy. You set up your
prefix to be
>
> EPREFIX=/Volumes/Gentoo
>
> and install everything into the image right from the
start, i.e.  
> bootstrap. That's the way I do it. Since the mount path
doesn't  
> change, you should be able to use it on any system.
>
> $ hdiutil create -size 5g -fs HFSX -volname Gentoo
-type SPARSE - 
> uid <numeric-portage-uid> -gid
<numeric-portage-gid> -attach  
> MyBrandNewGentoo.sparseimage
>
> will create a new sparseimage holding 5g, which you can
install  
> prefix into. To actually mount this with portage
user/group  
> settings, you have to select the mounted image in the
Finder and  
> "Enable Owners". A sparseimage is a dmg that
eats up only as much  
> space as necessary (+ fs-overhead). If you create and
delete lots  
> of stuff in a sparseimage, you should run
>
> $ hdiutil compact MyBrandNewGentoo.sparseimage
>
> every once in a while. (If you use encrypted home dirs,
you already  
> know this - it's what happens when you click ok to the
reclaim  
> space dialog after logout.)
>
> As Fabian already mentioned, EPREFIX gets hardcoded in
tons of  
> places, so there's no way of changing it after
bootstrap. The only  
> other solution I can think of is creating a symling
>
> $ ln -s /Volumes/Gentoo $
>
> but you might as well use a dmg to start with.
>
> Tobias
>
> Am 09.02.2007 um 23:10 schrieb Fabian Groffen:
>
>> On 09-02-2007 23:03:50 +0100, Frank Groeneveld
wrote:
>>> I was trying to create a
"prefix-portage-installer" dmg and ran into
>>> the following problem.
>>> When portage is installed in the tarball, it's
not possible to  
>>> get it
>>> to install in a different EPREFIX then the one
it was compiled with.
>>
>> Duh.
>>
>>> Example:
>>>
>>> $ EPREFIX=/bla emerge --info
>>> Portage 2.1.20.5894
(default-darwin/macos/10.4/x86, gcc-4.0.1,
>>> unavailable, 8.8.1 i386)
>>>
============================================================
=====
>>> System uname: 8.8.1 i386 i386
>>> Gentoo Prefix Base System version 1.12.5
>>>
>>> ...
>>> EPREFIX=/Volumes/GentooPrefix/
>>> ...
>>>
>>> Even defining it in etc/make.conf doesn't seem
to help.
>>> Is this a bug or am I doing something wrong
here...
>>
>> EPREFIX is a variable that is never set or
overridden.  You would  
>> simply
>> screw up your install if you would do, as portage
would get  
>> clueless as
>> to where to find what.
>>
>>> When I get this fixed, we will have a very easy
to use bootstrap dmg
>>> which you can mount and then run emerge -e
system to install in  
>>> EPREFIX.
>>
>> Well, I don't see a nice way out, and instead, I
just would  
>> suggest you
>> to set your path to include the dmg, and then
bootstrap portage.  The
>> configure stuff of portage allows you to split
install and eprefix
>> paths, but imho that only complicates matters.
>>
>> -- 
>> Fabian Groffen
>> Gentoo on a different level
>>
>> -- 
>> gentoo-altgentoo.org mailing list
>>
>
> -- 
> gentoo-altgentoo.org mailing list
>

-- 
gentoo-altgentoo.org mailing list

On Sat, 2007-02-10 at 19:58 +0100, Frank Groeneveld wrote:
> I know how this works, but this is not the way grobian
and genstef  
> want to create an "installer".
> They want to provide a .dmg that contains the necessary
tools to run  
> an emerge -e system to a specific location.
> So you can download the dmg, mount it, set some env
variables and  
> then start installing prefix-portage in, for example
/Library/Gentoo.

I'm sure you're looking for attached patch. Yes, it can work
that easy,
and the patch should be enough to start playing.

To do 'EPREFIX=/bla emerge --info' it is enough to have
existing empty
directory '/bla'...

Good luck,
/haubi/

> 
> Frank
> 
> Op 10-feb-2007, om 2:15 heeft Tobias Hahn het volgende
geschreven:
> 
> > Actually, the solution is quite easy. You set up
your prefix to be
> >
> > EPREFIX=/Volumes/Gentoo
> >
> > and install everything into the image right from
the start, i.e.  
> > bootstrap. That's the way I do it. Since the mount
path doesn't  
> > change, you should be able to use it on any
system.
> >
> > $ hdiutil create -size 5g -fs HFSX -volname Gentoo
-type SPARSE - 
> > uid <numeric-portage-uid> -gid
<numeric-portage-gid> -attach  
> > MyBrandNewGentoo.sparseimage
> >
> > will create a new sparseimage holding 5g, which
you can install  
> > prefix into. To actually mount this with portage
user/group  
> > settings, you have to select the mounted image in
the Finder and  
> > "Enable Owners". A sparseimage is a dmg
that eats up only as much  
> > space as necessary (+ fs-overhead). If you create
and delete lots  
> > of stuff in a sparseimage, you should run
> >
> > $ hdiutil compact MyBrandNewGentoo.sparseimage
> >
> > every once in a while. (If you use encrypted home
dirs, you already  
> > know this - it's what happens when you click ok to
the reclaim  
> > space dialog after logout.)
> >
> > As Fabian already mentioned, EPREFIX gets
hardcoded in tons of  
> > places, so there's no way of changing it after
bootstrap. The only  
> > other solution I can think of is creating a
symling
> >
> > $ ln -s /Volumes/Gentoo $
> >
> > but you might as well use a dmg to start with.
> >
> > Tobias
> >
> > Am 09.02.2007 um 23:10 schrieb Fabian Groffen:
> >
> >> On 09-02-2007 23:03:50 +0100, Frank Groeneveld
wrote:
> >>> I was trying to create a
"prefix-portage-installer" dmg and ran into
> >>> the following problem.
> >>> When portage is installed in the tarball,
it's not possible to  
> >>> get it
> >>> to install in a different EPREFIX then the
one it was compiled with.
> >>
> >> Duh.
> >>
> >>> Example:
> >>>
> >>> $ EPREFIX=/bla emerge --info
> >>> Portage 2.1.20.5894
(default-darwin/macos/10.4/x86, gcc-4.0.1,
> >>> unavailable, 8.8.1 i386)
> >>>
============================================================
=====
> >>> System uname: 8.8.1 i386 i386
> >>> Gentoo Prefix Base System version 1.12.5
> >>>
> >>> ...
> >>> EPREFIX=/Volumes/GentooPrefix/
> >>> ...
> >>>
> >>> Even defining it in etc/make.conf doesn't
seem to help.
> >>> Is this a bug or am I doing something
wrong here...
> >>
> >> EPREFIX is a variable that is never set or
overridden.  You would  
> >> simply
> >> screw up your install if you would do, as
portage would get  
> >> clueless as
> >> to where to find what.
> >>
> >>> When I get this fixed, we will have a very
easy to use bootstrap dmg
> >>> which you can mount and then run emerge -e
system to install in  
> >>> EPREFIX.
> >>
> >> Well, I don't see a nice way out, and instead,
I just would  
> >> suggest you
> >> to set your path to include the dmg, and then
bootstrap portage.  The
> >> configure stuff of portage allows you to split
install and eprefix
> >> paths, but imho that only complicates
matters.
> >>
> >> -- 
> >> Fabian Groffen
> >> Gentoo on a different level
> >>
> >> -- 
> >> gentoo-altgentoo.org mailing list
> >>
> >
> > -- 
> > gentoo-altgentoo.org mailing list
> >
> 

What I was thinking of is that the value of EPREFIX gets
hardcoded in  
various shebangs, libraries, python scripts...

Don't you think this is an issue?

Tobias

Am 13.02.2007 um 13:05 schrieb Michael Haubenwallner:

> I'm sure you're looking for attached patch. Yes, it can
work that  
> easy,
> and the patch should be enough to start playing.
>
> To do 'EPREFIX=/bla emerge --info' it is enough to have
existing empty
> directory '/bla'...

-- 
gentoo-altgentoo.org mailing list

On Tue, 2007-02-13 at 13:28 +0100, Tobias Hahn wrote:
> What I was thinking of is that the value of EPREFIX
gets hardcoded in  
> various shebangs, libraries, python scripts...
> 
> Don't you think this is an issue?

It is not more or less an issue than doing this with the
bootstrap
script. It is not an issue for portage itself.

Doing 'emerge -e system' in the new prefix still is required
(having
EPREFIX unset) to detach from the bootstrap prefix.

Using 'EPREFIX=... emerge' just helps _bootstrapping_
another prefix
using an existing instance.

One difference is that there is no need to do the
"-collision-protect"
merge of _same_ portage version as used for bootstrap.

/haubi/


> 
> Tobias
> 
> Am 13.02.2007 um 13:05 schrieb Michael Haubenwallner:
> 
> > I'm sure you're looking for attached patch. Yes,
it can work that  
> > easy,
> > and the patch should be enough to start playing.
> >
> > To do 'EPREFIX=/bla emerge --info' it is enough to
have existing empty
> > directory '/bla'...
> 

-- 
gentoo-altgentoo.org mailing list

OK, then we agree 

Tobias

Am 13.02.2007 um 14:16 schrieb Michael Haubenwallner:

> On Tue, 2007-02-13 at 13:28 +0100, Tobias Hahn wrote:
>> What I was thinking of is that the value of EPREFIX
gets hardcoded in
>> various shebangs, libraries, python scripts...
>>
>> Don't you think this is an issue?
>
> It is not more or less an issue than doing this with
the bootstrap
> script. It is not an issue for portage itself.
>
> Doing 'emerge -e system' in the new prefix still is
required (having
> EPREFIX unset) to detach from the bootstrap prefix.
>
> Using 'EPREFIX=... emerge' just helps _bootstrapping_
another prefix
> using an existing instance.
>
> One difference is that there is no need to do the
"-collision-protect"
> merge of _same_ portage version as used for bootstrap.
>
> /haubi/
>
>
>>
>> Tobias
>>
>> Am 13.02.2007 um 13:05 schrieb Michael
Haubenwallner:
>>
>>> I'm sure you're looking for attached patch.
Yes, it can work that
>>> easy,
>>> and the patch should be enough to start
playing.
>>>
>>> To do 'EPREFIX=/bla emerge --info' it is enough
to have existing  
>>> empty
>>> directory '/bla'...
>>
>
> -- 
> gentoo-altgentoo.org mailing list
>

-- 
gentoo-altgentoo.org mailing list