Gentoo Archives: gentoo-alt

From: Fabian Groffen <grobian@g.o>
To: gentoo-alt@l.g.o
Subject: Re: [gentoo-alt] Portability of Prefixed installs?
Date: Wed, 25 Jun 2008 19:36:55
Message-Id: 20080625193649.GJ707@gentoo.org
In Reply to: Re: [gentoo-alt] Portability of Prefixed installs? by Peter Abrahamsen
1 On 25-06-2008 12:25:57 -0700, Peter Abrahamsen wrote:
2 > Hi Fabian,
3 >
4 > On Jun 24, 2008, at 11:50 PM, Fabian Groffen wrote:
5 >> Portage is not designed to be "handed over" to anyone. However, there
6 >> should be just one place in Portage itself where the user is set (this
7 >> pym/portage/const_autotool.py). It may implicitly encode it in
8 >> installed packages, but this is due to the nature of those packages
9 >> that
10 >> do that themselves.
11 >
12 > Fair enough, but couldn't that script just set it to ${USER}? Is there
13 > something unsafe about that?
14
15 Uhm... well, if you would do that you:
16 a) would allow anyone to emerge/unmerge anything in your prefix
17 b) would get loads of permission denied errors lateron, since the files
18 are still owned by you, not by random ${USER}
19
20 Could go and mess with permissions here, but then why not create a user
21 that everyone can sudo to or something. Well, anyway, it's similar to
22 user A installing a package X, and user B wanting to update/remove X.
23
24 >> Maybe one of the two following things is interesting to you:
25 >> - binary packages
26 >> Prefix Portage can install from binary packages made for "another"
27 >> Prefix. You could use them to get each developer to quickly get up
28 >> to
29 >> speed, in their own Prefix installation.
30 >
31 > Actually, that's a really good idea, I hadn't thought of using binary
32 > packages with prefix.
33 >
34 > I'm in the process of moving management of our servers into puppet
35 > (http://puppet.reductivelabs.com/), which I'm also using to distribute
36 > our overlay. There's no reason our prefixed installs couldn't use this as
37 > well, allowing us to ensure that everyone has the right version of the
38 > core dependencies of our project (installed via binary package) without
39 > blowing away anything they might have going on.
40
41 "Our" binpackages on tinderbox.dev.gentoo.org (default-prefix dir) are
42 not too up-to-date, and mostly missing, but you can get an idea of how
43 it works. If you point PORTAGE_BINHOST to the url (http is fine)
44 `emerge -Kav` should do it (I may be wrong in the flags, have to look it
45 up). Of course your own binhost can contain optimised packages (if you
46 know the systems) specific USE-flags, and just only what you need. This
47 in combination with a prefix-macos-kick-start.dmg should be able to get
48 you up to speed in no-time. (Disclaimer: not tested ;) ) The
49 prefix-macos-kick-start.dmg is on my todo/wish-list still.
50
51 > Thanks to all contributers for your work, it's really nice to be able to
52 > manage my OS X box with the tools I already know.
53
54 Thank you for using the work we put so much efforts in to make it rock.
55
56
57 --
58 Fabian Groffen
59 Gentoo on a different level
60 --
61 gentoo-alt@l.g.o mailing list