Date: Wed, 20 Aug 2025 09:01:11 -0700 From: Mark Millard <marklmi@yahoo.com> To: Colin Percival <cperciva@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports" Message-ID: <4D89699D-D035-4C92-AA13-1DBEDA798358@yahoo.com> In-Reply-To: <08E5838F-122B-4CF6-8551-85095024A665@yahoo.com> References: <05CD2AAD-31EA-471B-8028-A3902D7A4192@yahoo.com> <5bece4af-0bec-457e-847f-7ca1cb031f86@freebsd.org> <E605DC69-27F4-4EF6-AFDE-D682A625131E@yahoo.com> <da2907f9-d3c5-4063-88dd-7219c55ed399@freebsd.org> <08E5838F-122B-4CF6-8551-85095024A665@yahoo.com>
index | next in thread | previous in thread | raw e-mail
[I was not thinking so well whenI asked some of the questions.
Sleep helped.]
On Aug 19, 2025, at 18:34, Mark Millard <marklmi@yahoo.com> wrote:
> On Aug 19, 2025, at 17:51, Colin Percival <cperciva@freebsd.org> wrote:
>
>> On 8/19/25 17:44, Mark Millard wrote:
>>> On Aug 19, 2025, at 17:25, Colin Percival <cperciva@freebsd.org> wrote:
>>>> Right, I don't see any reason for having separate files. If I thought people
>>>> might want to delete one of them (e.g. rm /etc/pkg/FreeBSD-base.conf in order
>>>> to disable pkgbase) then I would separate them; but the recommended way to
>>>> disable a repository is with an {enabled: no} in /usr/local/etc/pkg/ so I
>>>> don't see any need to separate these.
>>> Will a pkgbase repo be present and enabled by default?
>>> present but disabled? Not present at all in
>>> /etc/pkg/FreeBSD.conf ?
>>> (I'm not trying to specify spelling for such here. But your
>>> note might be better with this intended spelling also
>>> being explicit so how it all fits together is more
>>> clear.)
>>> If /etc/pkg/FreeBSD.conf is intended not to be edited at all
>>> by default, that might have implications for some default
>>> content there or inside /usr/local/etc/pkg/repos/ someplace
>>> if pkgbase is not enabled by default.
>>> (My understanding is that pkgbase is off by default.)
>>
>> pkgbase is off by default in 14 but will be on by default in 15.
>
> With 15 or main [then: 16] as the context . . .
>
> Will buildworld buildkernel installkernel installworld (not
> referencing various steps) for folks using source code based
> updates need to undo an addition of pkgbase from the
> installworld activity? Never? Just once? Each time?
>
> Or is "on by default" more selective somehow for such
> contexts?
/usr/local/etc/pkg/repos/*.conf override /etc/pkg/FreeBSD.conf
and the /usr/local/etc/pkg/repos/*.conf are not modified by
installworld . This is nothing new.
Sorry for the noise.
A similar point goes for file naming and content partitining:
/usr/local/etc/pkg/repos/*.conf
need not match the naming or content partitioning used in
/etc/pkg/ . /etc/pkg/ can be left as FreeBSD would initialize
it.
> Note: In my context I'll have pkgbase in use for the
> booted world and available for use as the booted kernel,
> although I'll have personal-build alternate kernels too.
> My from-source installed world will be in, for example, a
> chroot directory tree(s) and in a poudriere jail world(s).
>
> I keep /usr/src/ for pkgbase to manage for itself and have
> a separate /usr/main-src/ (as an example).
>
> So I'll be dealing with both types of contexts no matter
> what.
>
>> People will
>> need it to update their systems for security updates, for example, since
>> freebsd-update is going away (at least in its present form -- it might turn
>> into a wrapper around pkg).
>>
>> Users who want to update the base system from another source (no pun intended)
>> will need to configure their systems appropriately.
>
===
Mark Millard
marklmi at yahoo.com
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D89699D-D035-4C92-AA13-1DBEDA798358>