From nobody Sun Jun 21 00:42:25 2026 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 4gjXbn30Q7z6hyKG for ; Sun, 21 Jun 2026 00:42:29 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [174.136.99.202]) (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 ECDSA (secp384r1) client-digest SHA384) (Client CN "oneyou.mgm51.net", Issuer "Mike's Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4gjXbm4jw5z3Nxb for ; Sun, 21 Jun 2026 00:42:28 +0000 (UTC) (envelope-from the.lists@mgm51.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=mgm51.com header.s=mgm51.com-10 header.b=HaCSAqow; dmarc=pass (policy=reject) header.from=mgm51.com; spf=pass (mx1.freebsd.org: domain of the.lists@mgm51.com designates 174.136.99.202 as permitted sender) smtp.mailfrom=the.lists@mgm51.com Received: from sentry.mgm51.net (sentry.mgm51.net [IPv6:2001:558:6017:e3:1130:5cc5:3dee:2458]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "sentry.mgm51.net", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 4gjXbk5qrtzHh0G for ; Sat, 20 Jun 2026 20:42:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mgm51.com; s=mgm51.com-10; t=1782002546; bh=QX5YaIor9ViiopyZyuFmtoO5ICw0oNLcYB/cMMh50jg=; h=Date:Subject:From; b=HaCSAqow7nF0F2gTai8doP5SefJVGAtYyRbLDR2QR3ATtO9hGwYs8FuwJuSRhoRHe wKrdT8lvawHeQ2jmVC6VUG9AALZyo6ty0neqtph/X2EkxKmLrFAmRKywsfvUBd26gu 7D32busS/PZ3AjiZf1PRPzTg8uNR/cL7N2LgpJO6yzsioo+u1DUICY/HC7NprHH5HK +bsqNDbA1XdedsSXcFqznEqUR6yGaj7oawItb4HCtNzLw+G8nbmWzPXVUKXKnMwDFb t4zFJ6nP8GPxeREAO5VvbQJ6x+WqhoNDxBKroVXnTscsAqbSIY/JEgTgKuMzku3+Al Ya50cE9SFhdZw== Received: from [10.11.2.100] (bigbloat.24cl.home [10.11.2.100]) by sentry.mgm51.net (Postfix) with ESMTP id 4gjXbj54K9zRcq3 for ; Sat, 20 Jun 2026 20:42:25 -0400 (EDT) Message-ID: <07752971-ba18-41f9-989b-ccdb88384a4c@mgm51.com> Date: Sat, 20 Jun 2026 20:42:25 -0400 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 List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Moving to pkg-based in 15.1 ... To: freebsd-pkgbase@FreeBSD.org References: Content-Language: en-US From: Mike In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-6.66 / 15.00]; DWL_DNSWL_MED(-2.00)[mgm51.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.962]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[mgm51.com,reject]; RCVD_IN_DNSWL_MED(-0.20)[174.136.99.202:from]; R_SPF_ALLOW(-0.20)[+ip4:174.136.99.202:c]; R_DKIM_ALLOW(-0.20)[mgm51.com:s=mgm51.com-10]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; FROM_HAS_DN(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-pkgbase@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-pkgbase@FreeBSD.org]; RCVD_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[mgm51.com:+] X-Spamd-Bar: ------ X-Rspamd-Queue-Id: 4gjXbm4jw5z3Nxb On 6/20/2026 8:15 PM, Mark Millard wrote: > I expect that, while rare, needing to touch a configuration file is > still a possibility for a patch release. I have yet to see on the FreeBSD wiki a way to essentially duplicate the simplicity of my prior script (sans config file changes) to update within a current release level. That prior script ~just worked.~ For years ... Indeed, your comment illustrates the new complexity that seems to have been introduced to a prior quite simple process.