Subject: Re: [PATCH builds.sr.ht 1/3] Use short version based on
 $openbsd_version instead of hardcoding set filenames
To: Drew DeVault <sir@cmpwn.com>, ~sircmpwn/sr.ht-dev@lists.sr.ht
References: <161392188026.13895.17993000693180821485-0@git.sr.ht>
 <161392188026.13895.17993000693180821485-1@git.sr.ht>
 <C9G426NMLMO3.32HXGJ9VNIC9Q@taiga>
From: Jarkko Oranen <oranenj@iki.fi>
Message-ID: <553784bd-8b8f-4fe6-b9ae-dcd7d07cfbfa@iki.fi>
Date: Mon, 22 Feb 2021 16:10:56 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <C9G426NMLMO3.32HXGJ9VNIC9Q@taiga>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 2/22/21 3:58 PM, Drew DeVault wrote:
> Why is this desirable? As far as I can tell, it introduces some hacks
> which we cannot expect to be reliable.

The problem with -current is that around release time, the filenames for 
current will be the same as the previous version (ie. after 6.9 is 
released, current will still be "6.9" for some time after that, despite 
the snapshots being newer). Without autodetecting the version number, 
the current image would break at random some time after release when the 
filenames change, requiring a patch to fix it.

There's a chance that the "autodetection" will break eventually too, but 
the OpenBSD repository structure has been fairly stable for a long time, 
so I'm willing to bet that it will break less often than once per
release cycle.

--
Jarkko