[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC changes in version numbering schemes
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Re: RFC changes in version numbering schemes
- From: Christopher JS Vance <openbsd_(_at_)_nu_(_dot_)_org>
- Date: Thu, 3 Nov 2005 14:30:18 +1100
On Thu, Nov 03, 2005 at 12:04:15AM +0100, Marc Espie wrote:
The idea is to add some v* suffix each time the numbering scheme changes.
- we still need the p* stuff to denote OpenBSD specific changes.
- v* versions mean we can go backwards. If we find a security issue,
and we have to go back from foo-2.0 to foo-1.9, then we just bump v* so
that it becomes foo-1.9v0, which is higher than foo-2.0...
Yes. Or if vendor numbering does strange things, although OpenBSD has
been good at straightening these out in the past.
The main objection you can have is that this is too complicated, but so
far, we haven't been able to find any hole in that scheme...
I believe you'll find FreeBSD uses '_' where OpenBSD currently uses
'p', and ',' where you're planning on 'v'. It seems to work for them.
So this has already been found useful, and has a working precedent.
... just as long as the numbering doesn't get so arcane you need a
silly dohickey to compare version numbers, like the one in glibc ...
+1 more vote of thanks for really good work on pkg_* - some of us have