Date: Thu, 16 Nov 2006 01:20:02 +0000 From: Shaun Amott <shaun@FreeBSD.org> To: Mike Brown <mike@skew.org> Cc: freebsd-ports@freebsd.org Subject: Re: how to keep PORTVERSION from going backwards? Message-ID: <20061116012001.GB13700@charon.picobyte.net> In-Reply-To: <200611150025.kAF0PMdv080454@chilled.skew.org> References: <200611150025.kAF0PMdv080454@chilled.skew.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--bAmEntskrkuBymla Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 14, 2006 at 05:25:21PM -0700, Mike Brown wrote: >=20 > How should I handle this? >=20 > The software vendor version numbers go like this: > 1.0b3 (older release) > 1.0 (current release) > 1.0.1 (upcoming release) >=20 > The port currently has PORTVERSION =3D 1.0.b3, and has not made use of=20 > DISTVERSION. >=20 > What's a good way to set PORTVERSION (and DISTVERSION, if needed) when I > update the port to the current and upcoming releases? I don't want the > PORTVERSION to go backwards. I assume that's what would happen if I set > it to just match the vendor's version numbers, and I assume that's bad. >=20 In this case, there is nothing special required, if you want to continue with the versions listed -- just set PORTVERSION. You can verify that the numbers sort correctly like so: % pkg_version -t 1.0.b3 1.0 < % pkg_version -t 1.0 1.0.1 < --=20 Shaun Amott // PGP: 0x6B387A9A "A foolish consistency is the hobgoblin of little minds." - Ralph Waldo Emerson --bAmEntskrkuBymla Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFFW7zBkmhdCGs4epoRAsZUAJ9K2j/wVGCkxiDdAziLYo/SNOrtkACgjXwF /tl+a/NqxL1JAltG0JdHfVM= =5ETQ -----END PGP SIGNATURE----- --bAmEntskrkuBymla--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061116012001.GB13700>