Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Jun 2026 21:19:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        pkgbase@FreeBSD.org
Subject:   [Bug 291501] Users should not be advised to overwrite /usr/local/etc/pkg/repos/FreeBSD.conf
Message-ID:  <bug-291501-36141-wAMnXV3yUY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-291501-36141@https.bugs.freebsd.org/bugzilla/>

index | next in thread | previous in thread | raw e-mail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291501

Michael Galassi <michael@galassi.us> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michael@galassi.us

--- Comment #5 from Michael Galassi <michael@galassi.us> ---
I wonder if instead of just fixing the overwrite issue we would not be doing
users a favor by making this a teachable moment. That comment could be replaced
by something more like:

# To disable any of the known repositories an override of this file should be
made in the
# /usr/local/etc/pkg/repos directory and a section for the repo which is no
longer wanted
# can be created which sets the enabled attribute to no.
# If the directory does not exist, it can be created with:
#    mkdir -p /usr/local/etc/pkg/repos
# If the file FreeBSD.conf does not exist therein, an empty file can be created
with:
#    touch /usr/local/etc/pkg/repos/FreeBSD.conf
# If the repo we wish to disable is the ports repository, it can be disabled
with:
#    echo "FreeBSD-REPO: { enabled: no }" >>
/usr/local/etc/pkg/repos/FreeBSD.conf
# Likewise, if you wish to enable a repository which is currently disabled,
this can
# be done with:
#    echo "FreeBSD-REPO: { enabled: no }" >>
/usr/local/etc/pkg/repos/FreeBSD.conf
# In both the above examples, the word REPO is to be replaced by the name of
the
# repository.  Currently understood repository names are "ports",
"ports-kmods", and
# "base".
# Further information on the content of pkg's configuration files can be found
in the
# pkg.conf man page which can be read with the command:
#    man 5 pkg.conf

I also wonder if the install scripts should really create a file in
/usr/local/etc which is critical to the upgradability of the system.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291501-36141-wAMnXV3yUY>