From nobody Thu Aug 21 13:56:38 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 4c74cR35fFz64wmB; Thu, 21 Aug 2025 13:56:39 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4c74cR2YH3z3syx; Thu, 21 Aug 2025 13:56:39 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1755784599; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=r5NELtbAL6O+hs+mS9DkKo6izyXgP+m78HNNQa9CGe8=; b=ZAr1qWH6/ebpNb0YLrdHwR1bGttV5UG3W/w17gCVoWmmDKqE15V5z1QH1gvXRtx0+kd8WW 4zEiieMobpA0J+CTQxsHQCbku76osta3TznqYkxH/Gs2VKbLABkWWOnmUQ4l1cceNYBnCA NUXyxgnjTS0yFoOAliUFGKlKRSM5hmaW2DYx663Jb/0H1aWsyGYSf2WKJODBBCYRfli/js 3IFO/OWXq8JxvIaVE6Rp6IPjF1DI52eq5cQcIWF2TV0m/jiwhrEPvcdo5eIPffq6pCA8MP mozDjzKK9sAHk5v/2ZUYY6Gyyy50UNyDg6oo0yjie+GAIUuGEqQob8RjvFaybQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1755784599; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=r5NELtbAL6O+hs+mS9DkKo6izyXgP+m78HNNQa9CGe8=; b=mP96YyrPqxud0zuwISml8cS8XJXTkyxCezGstRBGvfuU+6aI5OrCVw1I+Yr9DgLr9goMwW qODzunRUQQ9CFV4BvHgn4KmiYeQF77dmqQGyeDgur9gQGsjP2xzRN67TwjNZpHd+BiGTwl +vOZSFnCINsxMuMRwIXWjTEK6hRUkfP2oE1VORO2sTxDNFkqKj/AmWbI47/jdTRhOVpLyi 5oQf6C+EdHLj/AUNaLqi92HUdeVBeR/k70VREKnPwitsQtWik/iYI47OWsyv/FoVyRNMuh zP62giZHtLUx56AjfB2mGIhB8NZHaefRR5H/TbNQY2rflXa9y09EO1xJi7rTaA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1755784599; a=rsa-sha256; cv=none; b=hHvWXk8Iil7u3FxNGwVHfKeAssH/ccDMI/Q+m+ogj34NVaOH7auEjpuzToqrVuLvh5AA2Y gv98C1+Gi3hdNAz+cC0z5xe2ja9Te5ruLqXPdy+p/r6DUwZbWY6B0rHZQF+swBFigcm/IE tDvrkYMTlGKNRGATtUo7vIvsdQxW+Vr3xJ70+GkC7kMYStlPxXdZTb/CmCbUnv/iQSMVx4 tmXB9fkII/KwuSRGTYJ1Hdiv72qZydk4CIezpoBuEq1tQSQodos5yXMZT7dXVudbloln9S eTWlxwql8vXxMlRF+K6eTVNWGVGd8mLnLMjo9bXCbCJ0xXhgOUA170uMwkc7Xw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [IPV6:2601:5c0:4202:5670:80cc:3c85:a16d:faed] (unknown [IPv6:2601:5c0:4202:5670:80cc:3c85:a16d:faed]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4c74cR0SD4z3ry; Thu, 21 Aug 2025 13:56:39 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: Date: Thu, 21 Aug 2025 09:56:38 -0400 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 User-Agent: Mozilla Thunderbird Subject: Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports" Content-Language: en-US To: Gleb Popov Cc: "freebsd-current@freebsd.org" , "freebsd-ports@FreeBSD.org" , FreeBSD Release Engineering Team References: <5d2daa68-cd27-4a56-9d69-5453b588a086@freebsd.org> <7c48e14d-b463-4523-8610-e18ac99f3381@FreeBSD.org> From: John Baldwin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 8/20/25 10:31, Gleb Popov wrote: > On Wed, Aug 20, 2025 at 5:22 PM John Baldwin wrote: >> >> On 8/20/25 01:54, Gleb Popov wrote: >>> On Wed, Aug 20, 2025 at 1:49 AM Colin Percival wrote: >>>> >>>> To reduce long-term confusion, I'm intending to rename the "FreeBSD" >>>> repository to "FreeBSD-ports", and similarly rename "FreeBSD-kmods" to >>>> "FreeBSD-ports-kmods". >>> >>> Having "ports" in the repository name does not make sense to me at >>> all. Ports are recipes to produce packages, but there are more ways (I >>> know at least one) to create a pkg package. >> >> But the packages in that repo are generated by FreeBSD ports? > > Yes, they are. Ok, if we're going full bikeshedding mode then I think that repos > should be named after what they represent rather than from what they are built. > That is, > - FreeBSD packages > - FreeBSD base packages > - FreeBSD kernel modules But then this last name is wrong. There are kernel modules in the base system as well, so that repository does not contain all of the project-provided kernel modules. > All right, maybe "FreeBSD packages" looks like a superset of the > latter two, so we can call it "FreeBSD main packages", which aligns > nicely with "FreeBSD quarterly packages". "main" vs "base" is not at all clear. Which one contains the package for /bin/ls? Is that in the "main" package set, or the "base" package set? Shouldn't the "main" package set contain the "main" parts of the system? (Or at least, isn't it conceivable that some users will think that and get inevitably confused?) I think using "ports" in the name is the best way to remove ambiguity. I would be fine, btw, with using "src" in the name for the base pkg repository. I can understand why the logical project is called pkgbase instead of pkgsrc to avoid conflicting the other pkgsrc project, but these descriptions seem clear to me: - "FreeBSD src" - "FreeBSD ports" - "FreeBSD ports kernel modules" And they could be named "FreeBSD-src" and "FreeBSD-ports" without having any single repository named just "FreeBSD". This better aligns with how we name the base system in other places (src.git, github/freebsd/freebsd-src.git, etc.) >>>> It defines a "FreeBSD" pkg repository which is in fact specifically bits >>>> maintained *outside* of FreeBSD (and packaged via the ports tree). >>> >>> Can't agree with this either. FreeBSD Ports are maintained *inside* >>> the project as well as package building and hosting infrastructure. It >>> feels perfectly fine to have a single configuration file named after >>> the *vendor*, which provides multiple repos maintained by that vendor. >> >> What if people only wish to use pkg.freebsd.org for base but not ports >> or vice versa? > > User can disable whatever repository he wants, it has nothing to do in > what config file this repo is declared. I had misinterpreted your suggestion to be that there should be a single "FreeBSD" repo that contained both base and ports packages. However, it does not seem that anyone is suggesting that thankfully. -- John Baldwin