Re: Packages with versions but no releases

[Jason Bacon <outpaddling%yahoo.com@localhost>]

On 2020-03-12 11:15, Brook Milligan wrote:
> I am making a package for software (rnaturalearthhires) that has version numbers but does not have any releases.  The only source seems to be a zip file with no version embedded in the name and the the project GitHub page lists 0 releases.
>
> My question is what to use as the pkgsrc version.  Options I see are:
>
> - Use the internal version.  This would seem to track what upstream is doing, but I am not sure what that number means relative to code updates and changes in the zip file.
>
> - Use my download date.  This seems to be the pattern for other unversioned packages and will readily differentiate different copies of the zip file.  However, if upstream starts doing proper releases, we have the problem of which is earlier, a date or a version?
>
> Thoughts?
>
> Cheers,
> Brook
For software with no versions at all, I have typically used something 
like 0.0.0.YYYYMMDD.

That way if/when they do start tagging releases with semantic 
versioning, it's pretty much guaranteed to upgrade properly.

It would be interesting to see what they say about their "internal" 
versions in this case, though.

    JB