From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] CONFIG_PROTECT and ROOT!='/'
Date: Tue, 15 Mar 2005 15:56:00 +0900 [thread overview]
Message-ID: <20050315065600.GA5908@ols-dell.iic.hokudai.ac.jp> (raw)
In-Reply-To: <1110860664.11759.3.camel@matrix.brianandsara.net>
[-- Attachment #1: Type: text/plain, Size: 2400 bytes --]
maillog: 14/03/2005-22:24:24(-0600): Brian Jackson types
> On Mon, 2005-03-14 at 13:21 -0800, Donnie Berkholz wrote:
> > Vitaly Ivanov wrote:
> > > I found the comments of Nicholas Jones in bug
> > > http://bugs.gentoo.org/show_bug.cgi?id=52415
> > >>> Portage makes the assumption that if you're installing
> > >>> into a new root, then you're building a system and
> > >>> shouldn't bother with config protection. It's not
> > >>> documented either way, so it's undefined behavior.
> >
> > I disagree with that logic, because people may be maintaining systems in
> > a ROOT with modified config files. Updating those systems trashes the
> > files. Thank you for pointing out this behavior now, because it walks
> > all over plans I have for a diskless cluster.
>
> I mentioned this to the portage guys the other day. Either they didn't
> care, or they didn't hear me. Either way, probably need to file a bug
> about it (or stir up that other one).
Alright! The bug is getting attention, and it even hasn't been a year!
I posted a patch at http://bugs.gentoo.org/show_bug.cgi?id=52415 that
addresses the issue. You can directly do
wget http://bugs.gentoo.org/attachment.cgi?id=53496 -O - | patch -p0
which will in turn screw your portage.py, but hopefully for the best.
As I see that there are more people who are interested in the bug, I am
expecting at least some to trust me enough as to try out the patch and
in turn make some noise (yeah, noise is what we need) when it makes them
happy.
The other problem that bothers me (that is: reading configuration
files from $ROOT) seems to be worked on. At least, there are
comments like:
# XXX: This should depend on ROOT?
if os.path.exists("/"+CUSTOM_PROFILE_PATH):
self.user_profile_dir = os.path.normpath("/"+"///"+CUSTOM_PROFILE_PATH)
self.profiles.append(self.user_profile_dir[:])
...
# XXX: Should depend on root?
self.mygcfg=getconfig("/"+MAKE_CONF_FILE,allow_sourcing=True)
if self.mygcfg == None:
self.mygcfg = {}
Which I guess means that it will sooner or later make it to the next
level in some form.
chutz out
--
*) Georgi Georgiev *) Live fast, die young, and leave a flat *)
(* chutz@gg3.net (* patch of fur on the highway! -- The (*
*) +81(90)6266-1163 *) Squirrels' Motto (The "Hell's Angels of *)
(* ------------------- (* Nature") (*
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-15 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 16:45 [gentoo-dev] CONFIG_PROTECT and ROOT!='/' Vitaly Ivanov
2005-03-14 21:21 ` Donnie Berkholz
2005-03-15 4:24 ` Brian Jackson
2005-03-15 4:24 ` Brian Jackson
2005-03-15 6:56 ` Georgi Georgiev [this message]
2005-03-15 14:26 ` Brian Jackson
2005-03-15 16:14 ` Georgi Georgiev
2005-03-15 18:01 ` Brian Jackson
2005-03-15 23:05 ` Georgi Georgiev
2005-03-16 3:17 ` Brian Harring
2005-03-16 3:35 ` Georgi Georgiev
2005-03-16 4:11 ` Brian Harring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050315065600.GA5908@ols-dell.iic.hokudai.ac.jp \
--to=chutz@gg3.net \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox