From owner-freebsd-questions@FreeBSD.ORG Thu Aug 5 13:08:31 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9C0916A4CE for ; Thu, 5 Aug 2004 13:08:31 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8475043D6A for ; Thu, 5 Aug 2004 13:08:29 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])i75D8HNF007219 for ; Thu, 5 Aug 2004 16:08:23 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) i75DA27L009342 for ; Thu, 5 Aug 2004 16:10:02 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost)i75DA0i4009338 for freebsd-questions@freebsd.org; Thu, 5 Aug 2004 16:10:00 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 5 Aug 2004 16:10:00 +0300 From: Giorgos Keramidas To: freebsd-questions@freebsd.org Message-ID: <20040805131000.GB9145@orion.daedalusnetworks.priv> References: <20040804065940.W87561@gaff.hhhr.ision.net> <20040805065414.46982.qmail@web51308.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040805065414.46982.qmail@web51308.mail.yahoo.com> Subject: Re: Can i make a CD of the Ports Collection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Aug 2004 13:08:32 -0000 ## Top-posting removed. ## Please do not top-post in the middle of a bottom-posting thread. On 2004-08-04 23:54, BSDjunkie wrote: >Olaf Hoyer wrote: >>On Wed, 4 Aug 2004, Peter Ryan wrote: >>> I am very new, and have been reinstalling FreeBSD many times to clean >>> up whatever mess i make and start again. >>> >>> I recently used cvsup to update my ports collection for the >>> 4.10_RELEASE. >>> >>> Now, when I reinstall, it takes much longer because i bring in the >>> updated ports collection rather than the ports collection on the >>> install CD (which i burnt from an ISO file) >> >> The whole portscollection is also available via ftp on ftp2.de.freebsd.org: >> [snip ftp get example] >> Simply download the tar.gz, and extract it to /usr/ports >> >> On each ISO of a release, like the 4.10R-CD #1, they take a snapshot of >> the ports tree when the make the assumption that it ist quite >> consistent. So when you download in say, 3 months a 4.10 ISO, the ports >> tree therein will be more than 3 months old. >> >> In that case, use whether cvsup or method above to get a recent ports >> tree. > > You can also reinstall the ports tree from the iso image. > > There's an install script on the cd that you can run if needed to > reinstall the release version of the ports tree. > > Updating should be done through cvsup if possible. I think that what the original poster meant is a bit different than this. When the /usr/ports tree is updated, the infrastructure bits that it contains will download updated, newer or fixed versions of the same ports if one tries to reinstall them. Since the release CD-ROMs do not contain the source files for these updated ports, they're downloaded over the network -- which can take a while if you're using a dialup connection or something similarly slow. The answer is that this cannot be avoided, since the source files of the new, updated versions of the packages were not available when the release CD-ROMs were prepared. To avoid downloading multiple times the same source files, I usually wait until one of my machines downloads the source tarballs and then burn a CD-ROM with the contents of my /usr/ports/distfiles or share this directory over NFS when that's possible. Peter, If you have a fast connection somewhere that can download these source files for you, you can copy the files from /usr/ports/distfiles from that machine to any other FreeBSD installation. The next time the ports try to locate the source tarball it's going to be where they expect it and no download will be attempted over the network. Giorgos