From nobody Thu Aug 21 15:36:06 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 4c76qn4jxmz65JV9; Thu, 21 Aug 2025 15:36:37 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-yw1-f176.google.com (mail-yw1-f176.google.com [209.85.128.176]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4c76qn2lWLz3HQQ; Thu, 21 Aug 2025 15:36:37 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-f176.google.com with SMTP id 00721157ae682-71d71bcab6fso9238007b3.0; Thu, 21 Aug 2025 08:36:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755790596; x=1756395396; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=JfXDmtfRikl+TmV41bykO0gxElBGvHisBDenfkOzBnY=; b=IBIKKtH9M4lh+UgKKbiMJXKuzg/XPUB/VvQ89xYnz4SCm1ef1Og9zNTt9yj2Z4rHXB RSZuqa59qCUIZupnyzZYuolz8aNsba5JalXHwMLO/TyeXdN5KW/fWpbuFnSoNOfpdh2P 86f6XQjdZOal3CjEV2EuqBsjEKGlDYcCbLz6oYGr/E3a3V0yi9Df+hinRkTksZa1exAm zGkAa7tULlzg4DzdR4CBh0b3yRjK9vmgwki6C75l6Di/RADkUKdw1j4eJnp0G0V1n6+E AccHhe7AG8+gn751+trvZDun8K/16OTDXc+oodmfqq/P5dRBS/oW/l2upkhP6wXy2GeR jsMQ== X-Forwarded-Encrypted: i=1; AJvYcCUk/th1wI4Y0UyiGPs2+MByj+Fw2kuzi+MGO6V/5mUogisIgzel1E985DY+ZAGa+BVDno47ZsNkZvppU2QE@freebsd.org, AJvYcCViAvGtR9R3vDZRnw7NKAyZHfT1UuJmNC48hbC2Kr5favQca8EOEBvuPrUb/aw4k4iJDK8=@freebsd.org X-Gm-Message-State: AOJu0YyGPIkzU1w0RgPE+8LTIyKbele9EfNh9L2ivG8oWCi7ti7D4fMh 1ZvEhMIDcmPoFgF2MmAN06JY9UlVXNcG2ZTcp4VAVeyaM7vFoQqt5wsigR/rHA== X-Gm-Gg: ASbGncuODu/c0XqRRUkDdUsNXWMNK2aXGsfMpIzpx/wC0FinbPYWS43sX4XLCUhOsji SwcW73Si+hSO9yeFLfnKnzLsm3d36IFtPTSXQViRFOCSVsdxfhP7T++jr/5+SJldKce2lrknR0k QUdTNX25R4O/nD8wGafznaaDy5OlzKdF9iskmGJndnWqEv+lNwr9an5yd1jqbu8hN/DoGRKCstl oVtDcxks8baToEzlEUDwdjZYWF3HYMbzJGHREzYwykM2hljzGLRHpY2DhSutkxFfIqR1OcAJugB nQk5csdhBqZfxFZ3SBSg09MCVQamiaeYDIwyE2V4dMA/PUuFUiTfTI8MD+lpno3K+7/Wl/ZJVrz BFeLef4kWEbl0uDJnR21y8kRM+PFXK7sWDHv1K/zzHA5u3+jTGWPbEaG+srwqKg== X-Google-Smtp-Source: AGHT+IGuDQuPtrpLl1NJFKHWB6OkwnRIrEPnK1qjNJVCQyfilt9PP4QcKclJim1sXmV4VWOgCv7zoA== X-Received: by 2002:a05:690c:6f09:b0:71a:1bbf:bc04 with SMTP id 00721157ae682-71fc89585d4mr36301267b3.19.1755790596091; Thu, 21 Aug 2025 08:36:36 -0700 (PDT) Received: from mail-yb1-f178.google.com (mail-yb1-f178.google.com. [209.85.219.178]) by smtp.gmail.com with ESMTPSA id 00721157ae682-71e6e058daesm44627477b3.39.2025.08.21.08.36.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 21 Aug 2025 08:36:34 -0700 (PDT) Received: by mail-yb1-f178.google.com with SMTP id 3f1490d57ef6-e94ea56725aso1222430276.2; Thu, 21 Aug 2025 08:36:34 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCVQ9dIQwgi93N/BpfsjE0r4hrNsdrRICRcS6fF7SjR1wdFIK1c9Q74JPMVVcRYZsF+37FGP48JOIsfuH8sB@freebsd.org, AJvYcCXMRU//rMprLjKbUxNwP5OpTd9MVV/HFdcSwqJ1abOdZ7p1wjmPEL4ztEa4ekYoVUeUgyM=@freebsd.org X-Received: by 2002:a05:6902:6d06:b0:e90:6f68:23c6 with SMTP id 3f1490d57ef6-e9508932594mr2904948276.22.1755790594168; Thu, 21 Aug 2025 08:36:34 -0700 (PDT) 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 References: <5d2daa68-cd27-4a56-9d69-5453b588a086@freebsd.org> <7c48e14d-b463-4523-8610-e18ac99f3381@FreeBSD.org> In-Reply-To: From: Gleb Popov Date: Thu, 21 Aug 2025 18:36:06 +0300 X-Gmail-Original-Message-ID: X-Gm-Features: Ac12FXwpgRcXXOwETU2nhyVdUynK6yjaKMzm6LulgHnGHCb6Rsx3LF-Ip5-Q0tY Message-ID: Subject: Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports" To: John Baldwin Cc: "freebsd-current@freebsd.org" , "freebsd-ports@FreeBSD.org" , FreeBSD Release Engineering Team Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4c76qn2lWLz3HQQ On Thu, Aug 21, 2025 at 4:56=E2=80=AFPM John Baldwin wrot= e: > > But then this last name is wrong. There are kernel modules in the base s= ystem > 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 ge= t > 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 thes= e > 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 n= ame > the base system in other places (src.git, github/freebsd/freebsd-src.git,= etc.) I don't want to bikeshed this further, mainly because I feel that discussions in mailing lists are too unstructured for this. A structured approach would be: 1. Decide what entity has the last word. srcmgr? pkgmgr? Maybe core? 2. Formulate what's wrong with current naming 3. Propose new naming and show how it improves upon the previous one. 4. Discussion phase 5. A ruling entity makes a final decision Luckily, I'm a low-ranking contributor enough to not have to decide on such important things.