Date: Sun, 25 Apr 2004 08:56:42 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Rahul Siddharthan <rsidd@online.fr> Cc: freebsd-current@freebsd.org Subject: Re: Valgrind for FreeBSD Message-ID: <20040425155642.GH78422@dragon.nuxi.com> In-Reply-To: <20040423172211.GA11368@online.fr> References: <1082737586.21666.11.camel@builder02.qubesoft.com> <20040423172211.GA11368@online.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 23, 2004 at 01:22:11PM -0400, Rahul Siddharthan wrote: > Doug Rabson wrote: > > > Please rename "valgrind-devel-port" to "valgrind-snapshot-port". > > > > I think I suggested the name valgrind-devel but I have no idea what the > > latest port naming conventions are. If valgrind-snapshot is more > > consistent, then thats the name it should have. > > Searching though the ports tree, I don't see any ports called > -snapshot. Some snapshot ports have a date stamp (eg, > gcc-3.3.4_20040322). There are dozens of -devel ports which are > unstable development versions of the regular ports (mutt-devel, > rxvt-devel, postgresql-devel, etc). We've had them in the past. > Many linux distributions use a -devel package for header files, which > they separate out from the main library package. Let's not go there. Yes, and FreeBSD has too.[*] This situaion is why "-devel" is a piss-poor name for these type of ports. "-snapshot" or "-indevel" are properly descriptive. -- -- David (obrien@FreeBSD.org) [*] And I would like to see a lot more of these, as I generally use Kris's packages vs. building from ports and I end up with a lot more crap on my system than I need.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040425155642.GH78422>