From nobody Mon Dec 8 16:16:58 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 4dQ6ZP2Kbcz6K222 for ; Mon, 08 Dec 2025 16:17:17 +0000 (UTC) (envelope-from peter@pean.org) Received: from helix.jails.se (system.jails.se [IPv6:2a05:d018:743:1603::4]) (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 4dQ6ZN2Y6kz3JP2 for ; Mon, 08 Dec 2025 16:17:16 +0000 (UTC) (envelope-from peter@pean.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pean.org header.s=856eb2587895cefc header.b="ADqC/fUK"; dmarc=none; spf=pass (mx1.freebsd.org: domain of peter@pean.org designates 2a05:d018:743:1603::4 as permitted sender) smtp.mailfrom=peter@pean.org Received: from smtpclient.apple (217-210-134-66-no2661.tbcn.telia.com [217.210.134.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by helix.jails.se (Postfix) with ESMTPSA id D4C7F178BF for ; Mon, 08 Dec 2025 17:17:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pean.org; s=856eb2587895cefc; t=1765210628; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=X0AvupI2Hxq2B24XMLRBMRLz/WZ6O4lzHt9CIYH14Xo=; b=ADqC/fUKwsdRyKw3NgGO2QnJYbmmZLMKMAtdpDeWtszWibPabi+CtvtTH70dhH3qj3OmmZ E61/zHi/jUQuwW52/yo8TOkNKLM3HbiPOFxL/MF7YSyatVmNazxDYLsHj/Kcjdx8YbIIBw AI+xdnpOx3fbeKXLmVTz+T+fJ0gOXmVsSvEi0FlBxTtp42ppA4A5XyofkboFjzJazJffDV 1B7X75J42yDCMhVuYruppruFyvmHeJaNvlIY9Fo8d9oH7JIp7p5U6fbGaWFQFq0+nm6yFn 0NCW0eZAGbOL0jJ0du/8208EUHFEES6X7EGYS8OJm8q3GWd6wCmCALlYTZ7xm2OiThZ71D EhRomugQP7pPzAqpfsfCp4yv6/r8ewXTr5maESmliEwKlWekNV86iIco5RLugtfEkvb3MV 5Fzl5Q+frzuwMOMTWDw46gro7fcvb7ew87uMe4jMClZI1KTTZUmtXP5yRuXV30n/D5uol+ 0NcGMT2rZbLucl1+ParhEo/YGUZDWExCXt2cQIC4HZbTDIYhh8i7sSrYGuQdxJom5PYCk0 p1Yw2yBX2td/vkP6eVLxbK+qbbHXSDHcz1lnqnDVbMeDsaSc76GguMCOd/yh6k6+qIzNkY ZexOohTlNxxblpuEmNbJXWhnAWAa3wHJnmJb4CN7e0KoNbxKPMGaE= From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= Content-Type: multipart/alternative; boundary="Apple-Mail=_8276DE63-7ADC-4288-8BB9-212184853A06" 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 (Mac OS X Mail 16.0 \(3826.600.51.1.1\)) Subject: Customize what packages get installed Message-Id: Date: Mon, 8 Dec 2025 17:16:58 +0100 To: freebsd-pkgbase@freebsd.org X-Mailer: Apple Mail (2.3826.600.51.1.1) X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.17 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.995]; R_MIXED_CHARSET(0.63)[subject]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[pean.org:s=856eb2587895cefc]; ONCE_RECEIVED(0.20)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[peter]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-pkgbase@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[pean.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-pkgbase@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[pean.org:+] X-Rspamd-Queue-Id: 4dQ6ZN2Y6kz3JP2 --Apple-Mail=_8276DE63-7ADC-4288-8BB9-212184853A06 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi! After fiddling around with pkgbase for a while realized that this is a = very convenient way to customize what software gets installed or = upgraded in a system compared to a custom make.conf. But after asking the forums = (https://forums.freebsd.org/threads/how-to-correctly-slim-down-a-base-syst= em-using-pkgbase.100605/) I haven=E2=80=99t found a documented way to do = this. If I for some reason like security, storage or any other reason decide = to build a slimmed down system I would like to filter what packages get = installed during upgrade. (I understand that first installation is a = different problem). Is there any production ready or recommended way to do this?=20 I could think of at least a few situations where this would be really = nice: * Embedded systems where storage is limited * High security systems where only the needed binaries should be = available * Single process jails I get that for jails I could just install the packages needed, but it = would be nice to have a standard way to choose the packages you need. A side track for this question is security updates. Using 14.3 upgrading = to a new patch level pkg upgraded all installed FreeBSD-base packages at = the new patch level. Why couldn=E2=80=99t it just install the packages = that changed with that patch level? I understand that the new repo has = to have all packages, but maybe there should be a way to signal to pkg = what packages are actually needed for that patch level. =20 Thanks! /Peter.= --Apple-Mail=_8276DE63-7ADC-4288-8BB9-212184853A06 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi!

After fiddling around with = pkgbase for a while realized that this is a very convenient way to = customize what software gets installed or upgraded in a system compared = to a custom make.conf.

But after asking the = forums (https://forums.freebsd.org/threads/how-to= -correctly-slim-down-a-base-system-using-pkgbase.100605/) I = haven=E2=80=99t found a documented way to do = this.

If I for some reason like security, = storage or any other reason decide to build a slimmed down system I = would like to filter what packages get installed during upgrade. (I = understand that first installation is a different = problem).

Is there any production ready or = recommended way to do this? 

I could think = of at least a few situations where this would be really = nice:
  * Embedded systems where storage is = limited
  * High security systems where only the needed = binaries should be available
  * Single process = jails

I get that for jails I could just install = the packages needed, but it would be nice to have a standard way to = choose the packages you need.

A side track for = this question is security updates. Using 14.3 upgrading to a new patch = level pkg upgraded all installed FreeBSD-base packages at the new patch = level. Why couldn=E2=80=99t it just install the packages that changed = with that patch level? I understand that the new repo has to have all = packages, but maybe there should be a way to signal to pkg what packages = are actually needed for that patch level. =  

Thanks!

/Peter.= --Apple-Mail=_8276DE63-7ADC-4288-8BB9-212184853A06--