Date: Thu, 17 Aug 2000 09:53:15 +1200 From: Jonathan Chen <jonathan.chen@itouch.co.nz> To: John Galt <galt@inconnu.isu.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: your mail Message-ID: <20000817095315.B6387@jonc.ntdns.wilsonandhorton.co.n> In-Reply-To: <Pine.LNX.4.21.0008161127370.17664-100000@inconnu.isu.edu>; from galt@inconnu.isu.edu on Wed, Aug 16, 2000 at 11:47:16AM -0600 References: <000001c006af$32f47960$798f6dcb@win98> <Pine.LNX.4.21.0008161127370.17664-100000@inconnu.isu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 16, 2000 at 11:47:16AM -0600, John Galt wrote:
>
> I've started to learn to despair of the ports tree ever getting the source
> tarballs right (pine4-ssl, rsaref, ad nauseum). You can get the
> canonical source from ftp.trilon.com and drop it in /usr/ports/distfiles,
> sacrifice a chicken to the gods of MD5 checksums, and pray that the
> patches aren't to a dead version.
Had that problem for a long time. The trouble is that the ports change
*all* the time, and one can only guarantee that the latest snapshort
of the ports will work. Using cvsup to sync the latest ports skeleton
is the only way to go. It will solve 90% of all build-from-ports
problems.
--
Jonathan Chen <jonathan.chen@itouch.co.nz>
----------------------------------------------------------------------
"A person should be able to do a small bit of everything,
specialisation is for insects"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000817095315.B6387>