public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] CONFIG_PROTECT and ROOT!='/'
Date: Mon, 14 Mar 2005 13:21:18 -0800	[thread overview]
Message-ID: <4236004E.1010007@gentoo.org> (raw)
In-Reply-To: <4235BFB0.70907@rle.ru>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCNgBOXVaO67S1rtsRAqwXAKD1gXa1Du1kUQl2SpmxGHKTIl+u3ACg++D1
yEnWNpiVD2Fhg97Tic7ZcFo=
=9nYL
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-03-14 21:22 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 [this message]
2005-03-15  4:24   ` Brian Jackson
2005-03-15  4:24     ` Brian Jackson
2005-03-15  6:56     ` Georgi Georgiev
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=4236004E.1010007@gentoo.org \
    --to=spyderous@gentoo.org \
    --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