Re: Unversioned and frequently updated data files?

[Paul Ripke <stix%stix.id.au@localhost>]

On Mon, Sep 08, 2025 at 06:28:35PM +1000, Paul Ripke wrote:
> On Sun, Sep 07, 2025 at 09:19:19AM -0400, Greg Troxel wrote:
> > Thomas Klausner <wiz%netbsd.org@localhost> writes:
> > 
> > >> What's the alternative in this situation? Simple leocad-data pkg with
> > >> checksums disabled?
> > >
> > > The standard method is to set DIST_SUBDIR to a date- or git-hash-based
> > > name and upload the distfile to ftp.NetBSD.org ('make upload') - if
> > > redistribution is allowed.
> > 
> > It's an upstream bug if they are distributing unversioned/variable
> > data, and I'd consider filing a report.   If the data is actually in a
> > version-control system you can perhaps use a tag or sha1-based version
> > to refer to to it that way and ignore their downloadable file.   An
> > example might be
> > 
> > 0.yyyymmdd.sha1
> > 
> > so that it sorts properly (sha1 hashes of course don't sort usefully).
> 
> The data isn't directly associated with the software.
> 
> afaict, there was a github mirror, but it hasn't been updated for a year.
> 
> It gets regularly released monthly, as a dated delta, and an un-dated,
> un-versioned full zipfile blob.
> 
> Software that consumes this appears to want the blob, and I guess users
> may want something more fresh than once-a-quarter updates?
> 
> I think I'm leaning towards a README at this point.

I also note that FreeBSD ports (cad/ldraw) took the datestamped distfile
subdir approach and is stuck at 20220211...

-- 
Paul Ripke
"Great minds discuss ideas, average minds discuss events, small minds
 discuss people."
-- Disputed: Often attributed to Eleanor Roosevelt. 1948.