From owner-freebsd-questions Wed Aug 16 14:54:12 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wilsonandhorton.co.nz (fw2.wilsonandhorton.co.nz [203.99.66.4]) by hub.freebsd.org (Postfix) with ESMTP id 991D237B531 for ; Wed, 16 Aug 2000 14:53:57 -0700 (PDT) (envelope-from jonc@itouch.co.nz) Received: (from jonc@localhost) by wilsonandhorton.co.nz (8.9.3/8.9.3) id JAA06827; Thu, 17 Aug 2000 09:53:15 +1200 (NZST) (envelope-from jonc) Date: Thu, 17 Aug 2000 09:53:15 +1200 From: Jonathan Chen To: John Galt Cc: freebsd-questions@FreeBSD.ORG Subject: Re: your mail Message-ID: <20000817095315.B6387@jonc.ntdns.wilsonandhorton.co.n> References: <000001c006af$32f47960$798f6dcb@win98> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from galt@inconnu.isu.edu on Wed, Aug 16, 2000 at 11:47:16AM -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 ---------------------------------------------------------------------- "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