Version numbering going forward?

magjac · July 23, 2020, 9:27pm

So we can’t use dash (-) in dev versions because RPM doesn’t allow it. After reading

github.com/semver/semver

conflict between a hyphen (-) in the version and rpmbuild

opened 01:51PM - 26 Jul 13 UTC

closed 06:43PM - 14 May 21 UTC

markgalassi

question consensus seeking

I decided to use your semver approach in its full glory for a new significant pr…oject. I think it's an important thing, and it would be good for people to just adopt it so we don't have so much variability. I have run in to one problem: I tagged a 0.1.0-alpha.0 release and I also set that to be the version in configure.ac (I'm using automake/autoconf) like this: AC_INIT([myproject], [0.1.0-alpha.1], [markgalassi@lanl.gov]) unfortunately this brings out an error when I build my tarball myproject-0.1.0-alpha.1.tar.gz and then build an RPM with rpmbuild -ta myproject-0.1.0-alpha.1.tar.gz I get this error: [markgalassi@beachhead _build]$ rpmbuild -ta myproject-0.1.0-alpha.1.tar.gz error: line 3: Illegal char '-' in: Version: 0.1.0-alpha.1 [markgalassi@beachhead _build]$ I build myproject.spec from a myproject.spec.in file which starts with: Name: @PACKAGE@ Version: @VERSION@ %define dateNoDashes %(date +"%Y%m%d") Release: %{dateNoDashes}%{?dist} and the myproject.spec comes out to be: Name: myproject Version: 0.1.0-alpha.1 %define dateNoDashes %(date +"%Y%m%d") Release: %{dateNoDashes}%{?dist} This seems to point to a conflict between a rather natural way of doing RPM specs and semver. I wonder how other people have resolved this. Right now I'm using 0.1.0alpha.1 as the version, but I'd rather stick to semver's spec. Another option would be to remove the hyphen when generating the spec file.

I settled for tilde (~) instead. Underscore would have been my second option.

Comments?