public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vitaly Ivanov <im@rle.ru>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] CONFIG_PROTECT and ROOT!='/'
Date: Mon, 14 Mar 2005 19:45:36 +0300	[thread overview]
Message-ID: <4235BFB0.70907@rle.ru> (raw)

Hello all

"To protect or not to protect..."

emerge tool overwrite files in CONFIG_PROTECT if ROOT != '/'

for example:
   CONFIG_PROTECT="/etc /opt/gentoos/hostname/root/etc"
   ROOT="/opt/gentoos/hostname/root/"
   emerge something
overwrite files in /opt/gentoos/hostname/root/etc

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.

But if I really want to overwrite those files
I can do it by
CONFIG_PROTECT="-*"
ROOT="/opt/gentoos/hostname/root/"
emerge something

I can't chroot to /opt/gentoos/hostname/root and emerge there,
because it is cross compilation and I can't protect those files
in any way now.

May be protect *all* files in CONFIG_PROTECT
even if ROOT != '/'
This behavior can be easy override by CONFIG_PROTECT="-*"
in command line if needed.

Thanks.


-- 
Vitaly Ivanov
email: va@mail.ru
icq uin: 15918498
--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2005-03-14 16:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 16:45 Vitaly Ivanov [this message]
2005-03-14 21:21 ` [gentoo-dev] CONFIG_PROTECT and ROOT!='/' Donnie Berkholz
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=4235BFB0.70907@rle.ru \
    --to=im@rle.ru \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@lists.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