Gentoo Archives: gentoo-dev

From: Brian Jackson <iggy@g.o>
To: gentoo-dev@××××××××××××.org
Subject: Re: [gentoo-dev] CONFIG_PROTECT and ROOT!='/'
Date: Tue, 15 Mar 2005 14:26:51
Message-Id: e10ff89ca54e8d044d9f4f9df11829ea@testdomain.com
In Reply to: Re: [gentoo-dev] CONFIG_PROTECT and ROOT!='/' by Georgi Georgiev
1 On 12:56:00 am 2005-03-15 Georgi Georgiev <chutz@×××.net> wrote:
2 > maillog: 14/03/2005-22:24:24(-0600): Brian Jackson types
3 > > On Mon, 2005-03-14 at 13:21 -0800, Donnie Berkholz wrote:
4 > > > Vitaly Ivanov wrote:
5 > > > > I found the comments of Nicholas Jones in bug
6 > > > > http://bugs.gentoo.org/show_bug.cgi?id=52415
7 > > > >>> Portage makes the assumption that if you're installing
8 > > > >>> into a new root, then you're building a system and
9 > > > >>> shouldn't bother with config protection. It's not
10 > > > >>> documented either way, so it's undefined behavior.
11 > > >
12 > > > I disagree with that logic, because people may be maintaining
13 > > > systems in a ROOT with modified config files. Updating those
14 > > > systems trashes the files. Thank you for pointing out this
15 > > > behavior now, because it walks all over plans I have for a
16 > > diskless cluster.
17 > > I mentioned this to the portage guys the other day. Either they
18 > > didn't care, or they didn't hear me. Either way, probably need to
19 > > file a bug about it (or stir up that other one).
20 >
21 > Alright! The bug is getting attention, and it even hasn't been a year!
22 >
23 > I posted a patch at http://bugs.gentoo.org/show_bug.cgi?id=52415 that
24 > addresses the issue. You can directly do
25 >
26 > wget http://bugs.gentoo.org/attachment.cgi?id=53496 -O - | patch -p0
27 >
28 > which will in turn screw your portage.py, but hopefully for the best.
29 >
30 > As I see that there are more people who are interested in the bug, I
31 > am expecting at least some to trust me enough as to try out the patch
32 > and in turn make some noise (yeah, noise is what we need) when it
33 > makes them happy.
34 >
35 > The other problem that bothers me (that is: reading configuration
36 > files from $ROOT) seems to be worked on. At least, there are
37 > comments like:
38
39 I have a bug filed for that too, but it's probably going to be a while
40 before it's fixed. From what I've been told, it's not trivial to fix it
41 because some of the config stuff isn't very well abstracted.
42
43 http://bugs.gentoo.org/show_bug.cgi?id=73350
44
45 --Iggy
46
47 >
48 > # XXX: This should depend on ROOT?
49 > if os.path.exists("/"+CUSTOM_PROFILE_PATH):
50 > self.user_profile_dir = os.path.normpath("/"+"///"+CUSTOM_PROF
51 > ILE_PATH)
52 > self.profiles.append(self.user_profile_dir[:])
53 >
54 > ...
55 >
56 > # XXX: Should depend on root?
57 > self.mygcfg=getconfig("/"+MAKE_CONF_FILE,allow_sourcing=True)
58 > if self.mygcfg == None:
59 > self.mygcfg = {}
60 >
61 >
62 > Which I guess means that it will sooner or later make it to the next
63 > level in some form.
64 >
65 > chutz out
66
67 --
68 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] CONFIG_PROTECT and ROOT!='/' Georgi Georgiev <chutz@×××.net>