On Thu, May 06, 2004 at 04:24:42PM -0500, Jacques A. Vidrine wrote:
> Another sticky area is e.g. openssh 3.8p2 versus 3.8.1p2. Under
> current rules, 3.8p2 > 3.8.1p2, which is obviously not intended by
> the ports committer. A workaround would have been to use 3.8.p2 <
> 3.8.1.p2. I don't particularly like that, because 3.8 > 3.8.p2 --- it
> wouldn't be a problem in practice, since all openssh portable versions
> have the `p', but it is ugly.
>
> This is really very similar to the previous thing... there is an
> inadvertant attempt to use `p' to add another level of structure to
> the version name. The problem is again clearer when it is viewed like
> so: 3.8.2 > 3.8.1.2.
>
> Hmm, I guess this might be part of why Oliver wanted to introduce a
> special behavior for `pl' ?
Some ports use "p1" for "patchlevel 1", some use it for "prerelease
version 1". Since we can't have it both ways, committers need to
remember to use pkg_version -t and some careful foresight to avoid
running version numbers backwards. However ultimately there will be
continue to be mistakes made, even if version monotonicity is somehow
enforced at commit-time.
Kris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD4DBQFAmq/pWry0BWjoQKURAjo3AJd1MgtiPkfylooLiHa5dQoVAc4/AKD+iSJ3
g2XQnkA7KEJZjfri8F+DBA==
=02kk
-----END PGP SIGNATURE-----