public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc
Date: Sat, 15 Jun 2024 18:00:07 -0400	[thread overview]
Message-ID: <QUNHZZ4M.GT7IR763.5TVF5P3M@LNES7F6U.OD2PYQCD.GAP47X4O> (raw)
In-Reply-To: <Zm02yDaKmI1X-NPM@phoenix.lan>

On 2024.06.15 02:38, Vitaliy Perekhovy wrote:
> On Fri, Jun 14, 2024 at 04:54:09PM -0400, Jack wrote:
> > I don't have any such directory.  What package does it belong to,  
> or is
> > it a config setting for portage or another package?
> 
> Yes, it is a configuration of portage itself. There is an env variable
> CONFIG_PROTECT that contains a list of directories that portage will
> protect from automatic modification. Please check this article:
> https://wiki.gentoo.org/wiki/CONFIG_PROTECT
> 
> You can query that variable by `portageq envvar CONFIG_PROTECT'.
/etc is the first entry in my CONFIG_PROTECT, but I still have no  
config-archive under /etc.  I think the folders listed in that variable  
are treated specially by portage in terms of not silently replacing  
config files, but doesn't control save/archive.

A bit of searching found the wiki page for dispatch-conf, which  
includes:

Before running dispatch-conf for the first time, the settings in  
/etc/dispatch-conf.conf should be edited, and the archive directory  
specified in /etc/dispatch-conf.conf will need to be created  
(/etc/config-archive by default).

So it appears that directory may be specific to that tool, and not  
directly related to portage.


  reply	other threads:[~2024-06-15 22:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 15:53 [gentoo-user] Difficulty with updating /etc/basb/bashrc Alan Mackenzie
2024-06-14 16:22 ` netfab
2024-06-14 17:33   ` Alan Mackenzie
2024-06-14 17:47     ` netfab
2024-06-14 17:52     ` netfab
2024-06-15 19:52       ` Alan Mackenzie
2024-06-15 11:39     ` Peter Humphrey
2024-06-16 14:26     ` [gentoo-user] " Nuno Silva
2024-06-14 18:25 ` [gentoo-user] " Vitaliy Perekhovy
2024-06-14 20:54   ` Jack
2024-06-15  6:38     ` Vitaliy Perekhovy
2024-06-15 22:00       ` Jack [this message]
2024-06-15 22:24         ` Peter Humphrey
2024-06-15 19:58   ` Alan Mackenzie
2024-06-14 23:43 ` Paul Colquhoun
2024-06-15  8:51   ` Re[2]: " Stefan Schmiedl
2024-06-15 20:10   ` Alan Mackenzie
2024-06-17  7:25     ` Wols Lists
2024-06-15 16:39 ` Wol
     [not found] <IPhvk-2UIJ-3@gated-at.bofh.it>
2024-06-14 16:19 ` Mike Civil
2024-06-14 17:39   ` Alan Mackenzie
2024-06-14 18:08     ` Waldo Lemmer
2024-06-15 17:14     ` Wol

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=QUNHZZ4M.GT7IR763.5TVF5P3M@LNES7F6U.OD2PYQCD.GAP47X4O \
    --to=ostroffjh@users.sourceforge.net \
    --cc=gentoo-user@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