0mGyhB/5NQ21SI5z1FlRHlUz5QN
         xlaKVJUaauZ5RU7h+k8gio2ECv1erxFb7toNJmtthcL83i1tCAL3I01mWdoflpi00g5j
         0yzNvwiGY/ptc7UE0a+SO2mXI4ncvG25a+6Hy+h5XjgZLEm0zOS18DNAdIyRL/tGYwk6
         o3zdlMDVS2pA8ElrYvwbr6wS1Yyl5CYjORdRtCV+ijRYGcGLjBVWDKPDtCm9ABQOJvF6
         EBuw==
X-Gm-Message-State: AOJu0Yy64SNfI8UgKaqt6UvDnO6xiNtLdqqQjCAoRdBFsy1nDz+GQfPG
	wUG7VByyYky4LsDAtqp4Mo+F2SXhpMN3AkS22/n3MmHX375z0kQR2ilqqM6mUWHzVS1S8bZDS4z
	lF7pd52mxmEEQ4eUPr7rt5ZbPuA2/kA==
X-Gm-Gg: ASbGncsjcHxFDMkxyPjWd16jd043/cim6FBHInEiWzb+luDD3162tSDrcAPVMnfg2FK
	EVLjgXeamI/r9590c0Sc9z07YQDB28BOJzItHqGhYo9Tk5AfoFHfiLBDFOn0v3CM903NWJ+Me
X-Google-Smtp-Source: AGHT+IFsLngVqhi+KTWdRJ2HYGsswE8fnKsnAeJ6688cp+dMC+ceSTknXybkrt93e4ePrenbwX8fBdJwfCY0jydeCpc=
X-Received: by 2002:a05:6602:15c2:b0:843:e9c1:9317 with SMTP id
 ca18e2360f4ac-844e8b9c9e8mr1057818839f.14.1734357076578; Mon, 16 Dec 2024
 05:51:16 -0800 (PST)
List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-current
List-Help: <mailto:freebsd-current+help@freebsd.org>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Subscribe: <mailto:freebsd-current+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-current+unsubscribe@freebsd.org>
Sender: owner-freebsd-current@FreeBSD.org
MIME-Version: 1.0
References: <CAPyFy2AXee_Y2xei176VAcW6peC0x=waxfPap+3uGG2o+ynv-A@mail.gmail.com>
 <iqguuu433aybga26gcvssmenxk24a6mhfkk5amxfbz62fqz2ic@4ddtkar7zvci>
In-Reply-To: <iqguuu433aybga26gcvssmenxk24a6mhfkk5amxfbz62fqz2ic@4ddtkar7zvci>
From: Ed Maste <emaste@freebsd.org>
Date: Mon, 16 Dec 2024 08:51:04 -0500
Message-ID: <CAPyFy2BLdw0A4cPknv02DQB3yY2nUQ_NqU+qHGU86=qhzFEatQ@mail.gmail.com>
Subject: Re: Switching release media dist sets to .tzst (tar + zstd)?
To: Shawn Webb <shawn.webb@hardenedbsd.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset="UTF-8"
X-Spamd-Result: default: False [-1.26 / 15.00];
	SUBJECT_ENDS_QUESTION(1.00)[];
	NEURAL_HAM_MEDIUM(-1.00)[-0.995];
	NEURAL_HAM_SHORT(-0.89)[-0.894];
	NEURAL_HAM_LONG(-0.47)[-0.470];
	FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com];
	R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17];
	DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none];
	MIME_GOOD(-0.10)[text/plain];
	FROM_HAS_DN(0.00)[];
	TO_DN_ALL(0.00)[];
	RCVD_TLS_LAST(0.00)[];
	RCPT_COUNT_TWO(0.00)[2];
	MIME_TRACE(0.00)[0:+];
	ARC_NA(0.00)[];
	MISSING_XM_UA(0.00)[];
	ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US];
	FREEFALL_USER(0.00)[carpeddiem];
	PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org];
	TO_MATCH_ENVRCPT_SOME(0.00)[];
	FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com];
	RCVD_COUNT_ONE(0.00)[1];
	MLMMJ_DEST(0.00)[freebsd-current@freebsd.org];
	RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.52:from];
	R_DKIM_NA(0.00)[];
	FREEMAIL_ENVFROM(0.00)[gmail.com];
	RCVD_IN_DNSWL_NONE(0.00)[209.85.166.52:from]
X-Rspamd-Queue-Id: 4YBhDj2vL9z4Nvl
X-Spamd-Bar: -

On Fri, 13 Dec 2024 at 16:47, Shawn Webb <shawn.webb@hardenedbsd.org> wrote:
>
> Hey Ed,
>
> Thanks for providing the opportunity to discuss this before landing
> it.

To be clear, this was just intended to explore the idea. I was looking
at some release artifact build infrastructure and was curious about
how extensive the changes would be.

> The tool for updating HardenedBSD installs (and the tool used to build
> the update artifacts) would be impacted. It wouldn't be too difficult
> to update the tools (hbsd-update and hbsd-update-build). However, if
> the switch zstd is not done at the same time for all supported
> branches (main and stable/14), we would need to have hbsd-update
> reference different archives between different branches--zstd for
> main and xz for stable/14. I would prefer not to have to include
> branch-specific code in a generic system updater utility.

Interesting, so you're using the dist sets for updates as well? This
is one good outcome of this discussion -- identifying different ways
folks are using the dist sets.