Date: Mon, 16 Dec 2024 08:51:04 -0500 From: Ed Maste <emaste@freebsd.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Switching release media dist sets to .tzst (tar + zstd)? Message-ID: <CAPyFy2BLdw0A4cPknv02DQB3yY2nUQ_NqU%2BqHGU86=qhzFEatQ@mail.gmail.com> In-Reply-To: <iqguuu433aybga26gcvssmenxk24a6mhfkk5amxfbz62fqz2ic@4ddtkar7zvci> References: <CAPyFy2AXee_Y2xei176VAcW6peC0x=waxfPap%2B3uGG2o%2Bynv-A@mail.gmail.com> <iqguuu433aybga26gcvssmenxk24a6mhfkk5amxfbz62fqz2ic@4ddtkar7zvci>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BLdw0A4cPknv02DQB3yY2nUQ_NqU%2BqHGU86=qhzFEatQ>