Date: Mon, 24 Jan 2005 15:43:40 +0100 From: Palle Girgensohn <girgen@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org>, Sean Chittenden <seanc@FreeBSD.org> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports UPDATING ports/databases/postgresql-devel Makefile Message-ID: <A9DBADFC77DE63728EF98768@rambutan.pingpong.net> In-Reply-To: <3FB436057021D7C93416454A@cc-147.int.t-online.fr> References: <20050123100627.35E4716A501@hub.freebsd.org> <3FB436057021D7C93416454A@cc-147.int.t-online.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
--On s=F6ndag, januari 23, 2005 11.22.50 +0100 Mathieu Arnold=20
<mat@FreeBSD.org> wrote:
> +-le 23/01/2005 10:06 +0000, Sean Chittenden =E9crivait :
>| seanc 2005-01-23 10:06:21 UTC
>| Port epoch bumped because 8.0.rc* is greater than 8.0.0.
>
> Note quite sure about that :
> $ pkg_version -t 8.0.rc5.2005.01.16 8.0.0
> <
Uh, 4.10 differs from 5.3 here:
FreeBSD 4.10$ pkg_version -t 8.0.0rc5 8.0.0
>
FreeBSD 4.10$ pkg_version -t 8.0rc5.2005.01.16 8.0.0
>
FreeBSD 5.3$ pkg_version -t 8.0.0rc5 8.0.0
<
FreeBSD 5.3$ pkg_version -t 8.0rc5.2005.01.16 8.0.0
<
portupgrade has it own algorithm. In conflict with pkg_version-5.3, it=20
considers 8.0.0rc or even 8.0.0beta to be greater than 8.0.0.=20
pkg_version-5.3 does the right thing, and to me it looks like the=20
portupgrade's algorithm for versioning is overly simple (I've never used=20
ruby though, perhaps it has some fancy operator overload stuff?):
cmp =3D newpkg.version <=3D> oldpkg.version
if cmp > 0
service =3D :upgrade
elsif cmp =3D=3D 0
service =3D :reinstall
else
service =3D :downgrade
end
I haven't checked if this is fixed in 4.11, but since it is not even out,=20
bumping port epoch is unfortunately necessary. :(
Palle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A9DBADFC77DE63728EF98768>