Date: Mon, 31 May 2004 10:22:20 +0200 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Akinori MUSHA <knu@iDaemons.org> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/databases/ruby-sqlrelay Makefile Message-ID: <40BAEB3C.6050200@fillmore-labs.com> In-Reply-To: <86r7t16wbf.knu@iDaemons.org> References: <200405301418.i4UEIVnF072175@repoman.freebsd.org> <86r7t16wbf.knu@iDaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Akinori MUSHA wrote: > At Sun, 30 May 2004 07:18:30 -0700 (PDT), > Oliver Eikemeier wrote: > >>eik 2004/05/30 07:18:30 PDT >> >> FreeBSD ports repository >> >> Modified files: >> databases/ruby-sqlrelay Makefile >> Log: >> fix PORTREVISION in this release > > Why? Didn't you read the commit log? The one who updated sqlrelay > just forgot to reset PORTREVISION of ruby-sqlrelay and it has never > been able to build, so no one can have ruby-sqlrelay 0.34.3_1 > installed and there should be no problem with the reset. I read the commit log, but the PORTREVISION reset is pureley cosmetic, so keeping it until the next release does not cause any problems. OTOH it makes automatic version auditing possible, which guarantees that tools like portupgrade will work. It is hard to check whether a port is just broken on a single platform or automatically read commit logs. If you want to have a version number going backwards, you can always bump PORTEPOCH. Do you think we need another mechanism/flag to signal automatic testing systems that everything is well? The script I'm running is at ports/Tools/scripts/chkversion.pl, feel free to send patches. Thanks for your feedback -Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40BAEB3C.6050200>