From nobody Thu Aug 7 15:02:32 2025 X-Original-To: freebsd-pkgbase@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 4byVl74LQZz64NGl; Thu, 07 Aug 2025 15:02:43 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtpo49.interia.pl (smtpo49.interia.pl [217.74.67.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4byVl229lLz3HCP; Thu, 07 Aug 2025 15:02:38 +0000 (UTC) (envelope-from vermaden@interia.pl) Authentication-Results: mx1.freebsd.org; none Date: Thu, 07 Aug 2025 17:02:32 +0200 From: vermaden Subject: Re: PKGBASE Removes FreeBSD Base System Feature To: Daniel Morante , "stable@freebsd.org" , "FreeBSD-pkgbase@freebsd.org" , freebsd-current X-Mailer: interia.pl/pf09 In-Reply-To: <73c44099-baa7-48b2-b486-1ffaf3017820@morante.net> References: <5d439128-fec3-4992-bb83-adcc440814cb@FreeBSD.org> <73c44099-baa7-48b2-b486-1ffaf3017820@morante.net> X-Originating-IP: 45.148.42.1 Message-Id: List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interia.pl; s=biztos; t=1754578955; bh=iLzUltVCBZP1zYTI1L/4iqOOBIgYmOscK7KXQONXAP4=; h=Date:From:Subject:To:Message-Id:MIME-Version:Content-Type; b=MdZLGlmfZH3CV6YMcsUK23pXHpXYH2CknqBh7iE6zqRccShXN+Nt/0IOIgzPiUb6L 98C4jZsRdvogL04AVEMW7r+o688BYdKX4DIzzs3WDmnEOwRZoGlY8AZ40YH7gq45ED lXAOtxNeO79LqJ0VBbZh4Jfu5SNalvyRQUtoHgaA= X-Rspamd-Queue-Id: 4byVl229lLz3HCP X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN_FAIL(0.00)[49.67.74.217.asn.rspamd.com:query timed out] > Why should we use the `pkg` tooling for this? > Why not instead have a dedicated set of tooling > for managing the base operating system? That is what I proposed here with pkgbase(8) command: https://lists.freebsd.org/archives/freebsd-pkgbase/2025-July/000596.html In point (1) of course. Temat: Re: PKGBASE Removes FreeBSD Base System Feature Data: 2025-08-07 16:58 Nadawca: "Daniel Morante" <daniel@morante.net> Adresat: stable@freebsd.org; FreeBSD-pkgbase@freebsd.org; "freebsd-current"= <freebsd-current@freebsd.org>;=20 >=20 >> I gave this more thought.  Maybe the problem here is the approach?  Why=20 > should we use the `pkg` tooling for this? >=20 > Why not instead have a dedicated set of tooling for managing the base=20 > operating system? We kind of already have that and it works well with=20 > the FreeBSD philosophy.  They are called `bsdinstall`, and=20 > `freebsd-update`.  Can we simply convert/repurpose (and maybe even=20 > merge) and rename those tools to handle managing the operating system in=20 > a package like style.  We just call it "freebsd-setup" or whatever.&= nbsp; The=20 > point being that `pkg` is for ports/packages for third party software=20 > and `freebsd-setup` is for the operating system.  The two should never=20 > cross paths. >=20 > On 8/7/2025 7:09 AM, DutchDaemon - FreeBSD Forums Administrator wrote: >> On 8/7/2025 1:43 AM, Tomek CEDRO wrote: >>> On Thu, Aug 7, 2025 at 12:21=E2=80=AFAM vermaden=20 wrote: >>>> So You still do not understand ... >>>> >>>> The pkg(8) command works fine - its just NOT SUPPOSE to DESTROY most=20 >>>> of the FreeBSD Base System - because FreeBSD is not Linux to allow >>>> shit like that ... >>> +1 =3D) >>> >>> Base and Userland should be clearly separated, as it was, as it is, no >>> matter how it will be organized internally (i.e. modular base) :-) >>> >>> Maybe its worth thinking about some sort of standard minimal fallback >>> environment (rescue?) when base gets broken for any reason (i.e. >>> broken pkgbase, broken modules, fs corruption, broken hardware, >>> accident) to either restore last working configuration or recreate >>> defaults with/from what can be saved? :-) >> >> >> Maybe this would be a good time to reserve the -b / --base flags in=20 >> pkg(8) .. ? >> >=20 >=20