From nobody Wed Aug 20 09:31:39 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4c6LnN4g0Mz64gYN; Wed, 20 Aug 2025 09:31:52 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4c6LnM5GhBz3nkQ; Wed, 20 Aug 2025 09:31:51 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (124-18-43-114.area1c.commufa.jp [124.18.43.114]) (authenticated bits=0) by www121.sakura.ne.jp (8.18.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 57K9Vee8042660; Wed, 20 Aug 2025 18:31:41 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1755682301; bh=oQ3v5k7ewPTDHjj99US63ViXmeQCP8cAhhUWkcENuq4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=C+ATiKnDgJXQihm/Z1Ky5/FYV6Hmav4eYSuqHxxT+1NJtbi2KTPSKcO2Ra2y6mB9K Jn7ymQVuLX1ncXB8W+orKcSMRTsIOn4/zT9CT0whSrMojXjgxetCVx+ThR8LkZ57WW sz18fItHibHxZmiOY8cR978u9D5Uuf+ml6+t+iAY= Date: Wed, 20 Aug 2025 18:31:39 +0900 From: Tomoaki AOKI To: Colin Percival Cc: Mark Millard , FreeBSD Current , FreeBSD Mailing List Subject: Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports" Message-Id: <20250820183139.07a25bf930db54bcd06b094b@dec.sakura.ne.jp> In-Reply-To: References: <05CD2AAD-31EA-471B-8028-A3902D7A4192.ref@yahoo.com> <05CD2AAD-31EA-471B-8028-A3902D7A4192@yahoo.com> <5bece4af-0bec-457e-847f-7ca1cb031f86@freebsd.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.3) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4c6LnM5GhBz3nkQ On Tue, 19 Aug 2025 17:51:22 -0700 Colin Percival wrote: > On 8/19/25 17:44, Mark Millard wrote: > > On Aug 19, 2025, at 17:25, Colin Percival 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. 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). +1 for keeping freebsd-update as a wrapper both for legacy and pkgbase. It would help users still need legacy (pre-pkgbase) version inside jail and/or bhyve that are installed from outside of jail / bhyve. Also, upgrading legacy version to pkgbase'ified version would be in consideration. Considering the use-cases with existing scripts in the wild, legacy options would be better kept as-is and introducing new option to use pkgbase. So would be bsdinstall. But once all non-pkgbase versions become EoL, the considerations would no longer mandatory. > Users who want to update the base system from another source (no pun intended) > will need to configure their systems appropriately. > > -- > Colin Percival > FreeBSD Release Engineering Lead & EC2 platform maintainer > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid -- Tomoaki AOKI