From owner-freebsd-ports Sun Apr 4 22:45:52 1999 Delivered-To: freebsd-ports@freebsd.org Received: from stennis.ca.sandia.gov (stennis.ca.sandia.gov [146.246.243.44]) by hub.freebsd.org (Postfix) with ESMTP id DCCAD14C24 for ; Sun, 4 Apr 1999 22:45:48 -0700 (PDT) (envelope-from bmah@stennis.ca.sandia.gov) Received: (from bmah@localhost) by stennis.ca.sandia.gov (8.9.3/8.9.3) id WAA19279; Sun, 4 Apr 1999 22:43:35 -0700 (PDT) Message-Id: <199904050543.WAA19279@stennis.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-Comptype: repl X-Exmh-Isig-Folder: Lists/freebsd-ports To: Michael Haro Cc: Sue Blake , freebsd-ports@FreeBSD.ORG Subject: Re: What do you think? In-Reply-To: Your message of "Sat, 03 Apr 1999 18:15:58 PST." <19990403181558.A91593@patrol.area51.fremont.ca.us> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-1392705644P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 04 Apr 1999 22:43:35 -0700 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==_Exmh_-1392705644P Content-Type: text/plain If memory serves me right, Michael Haro wrote: > On Sun, Apr 04, 1999 at 11:52:40AM +1000, Sue Blake wrote: > > On Sat, Apr 03, 1999 at 05:14:11PM -0800, Michael Haro wrote: > > > What do you think about creating some sort of variable in the > > > Makefile like NEXT_VERSION or something which contains either a > > > regular expression or printf like format string so that a script > > > can go through the ports and check for new versions. [request for clarifications] > My idea was actually to help the ports maintainers know when a new version > of the source for a program they are responsible for is out. As someone who maintains several ports, my first reaction is that while automating newer version detection is neat, it's not clear how useful it'd be. A *newer* version isn't necessarily a *better* one, and there's going to be some human judgement involved to decide what the right thing to do is. Look at ports such as tcl or gtk, which have (or had) multiple versions lying around the ports tree, or the localized versions of various ports. What if the distfiles move? What if they change without changing version numbers (vnc did this several times)? Are you sure you can even determine what's "newer" with a regexp match against the version number (as a hint, pkg_version tries, but it doesn't always succeed)? (I don't meant to mock your idea...I'm just pointing out some of the subtle difficulties involved, many of which I ran into while writing pkg_version.) For me, I consider it part of my "job" as a port maintainer to have at least a vague idea of what's happening in terms of continuing development for that piece of software, whether it be by reading the appropriate mailing list or by polling the appropriate Web pages every so often. Additionally, if I *do* miss a useful update, a fellow user is bound to point this out pretty quickly. > If you are looking for a utility to tell you if there is a newer version > of a port already in existance than the version you have installed, take > a look at the sysutils/pkg_version port. Thanks for the reference...this reminds me that I have a whole pile of submitted patches for pkg_version that I need to wade through... :-) Cheers, Bruce. --==_Exmh_-1392705644P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNwhNhqjOOi0j7CY9AQEABgP+I4NcP2HdUshtipnsZuxImXRfhnhk23GT +/xjpy+7G0+CxPfNaE6JJ5uPwnHXB3CP2W99B25WYLcrAS0+SOEcr4Zk5twt25RG f8oVSMA7VJMcylQDNu/ZO/C1xuzlWa9m7w0fkIGvNxqw2opwDOBnvLm/rJsIFlTR BErscjpA5kM= =5IL2 -----END PGP MESSAGE----- --==_Exmh_-1392705644P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message