Re: handling versioning change

[Filip Hajny <filip%joyent.com@localhost>]

> 27. 11. 2016 v 15:31, Joerg Sonnenberger <joerg%bec.de@localhost>:
> 
> On Sat, Nov 26, 2016 at 10:45:57AM -0500, Greg Troxel wrote:
>>  1) just change the version and people will have to deal, once
> 
> Just make sure to add some appropiate limits to avoid the old version
> where necessary.
> 
>>  2) do something like 132.1.7.3 and be kludgy forever
> 
> More like go with 999a1.7.3 or so. That's reasonable dense and still
> orders well.
> 
>>  3) Implement some silent metadata in versions just for tools that
>>  check versons, so that the human-presented version is right.  I dimly
>>  recall discussion of this (EPOCH?) but can't find it.
> 
> All epoch syntaxes are more or less as bad as the above, some just stick
> the marker to the end.

Thanks for the discussion, everyone. I made up my mind and simply changed the version. lz4 is a minor package with a limited dependent tree, so the fallout should not be drastic.

-F