Andrew Edwards, el 21 de January a las 20:06 me escribiste: > On 1/21/14, 6:02 PM, Jordi Sayol wrote: > >El 21/01/14 23:29, Brad Anderson ha escrit: > >> #.###.~b# ==> 2.065.b1 // beta > >> #.###.~rc# ==> 2.065.rc1 // release candidate > >> #.###.0 ==> 2.065.0 // initial release > >> #.###.# ==> 2.065.1 // hotfix > > > >On Debian, "2.065.rc1" is bigger than "2.065.0", so if > >"dmd_2.065.rc1-0_amd64.deb" is installed and you try to upgrade to > >"dmd_2.065.0-0_amd64.deb", system will answer something like "You have > >installed a newer version". > > > >No problem if these deb packages are for internal use and test, but not for > >a public download. > > > >$ dpkg --compare-versions "2.065.0" gt "2.065.rc1" && echo "Bigger" || echo > >"Not bigger" > > > > Apparently the same problem exists on FreeBSD. The first solution > that comes to mind is to prefix the qualifiers for betas and release > candidates with a tilde. As such: > > 2.065~b1 > 2.065~rc1 > > or: > > 2.065.~b1 > 2.065.~rc1 > > This solution works on both Ubuntu and FreeBSD but I'm not sure it > is the right one. Suggestions are welcomed.
There is a fairly popular de-facto standard for versioning: semver. Yes, it is incompatible with Debian (and I guess FreeBSD) but you can make it compatible by just changing one character ("-" -> "~"). Since apparently a version naming scheme is needed, does anyone have a good reason NOT to use a standard that's easily adaptable to several popular distributions? -- Leandro Lucarella (AKA luca) http://llucax.com.ar/