From owner-freebsd-questions Wed Jan 31 15:40:41 2001 Delivered-To: freebsd-questions@freebsd.org Received: from harumscarum.mr.itd.umich.edu (harumscarum.mr.itd.umich.edu [141.211.125.17]) by hub.freebsd.org (Postfix) with ESMTP id B8EE237B491 for ; Wed, 31 Jan 2001 15:40:23 -0800 (PST) Received: from tim.elnsng1.mi.home.com (c1129767-a.elnsng1.mi.home.com [24.183.248.20]) by harumscarum.mr.itd.umich.edu (8.9.3/3.3s) with SMTP id SAA29890; Wed, 31 Jan 2001 18:40:13 -0500 (EST) From: Tim McMillen To: Christopher Farley , "Geoffrey Crompton (RMIT Guest)" Subject: Re: getting ports to work Date: Wed, 31 Jan 2001 18:44:12 -0500 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-questions@FreeBSD.ORG References: <20010201093204.A23055@gecko.eric.net.au> <20010131171011.C6064@northernbrewer.com> In-Reply-To: <20010131171011.C6064@northernbrewer.com> MIME-Version: 1.0 Message-Id: <01013118441205.83787@tim.elnsng1.mi.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday January 31, 2001 18:10, Christopher Farley wrote: > Geoffrey Crompton (RMIT Guest) (ghcrompton@gecko.eric.net.au) wrote: > > I've got a machine here that was recently upgraded from 4.1.1 to > > 4.2. That went fine, but now the ports collection don't work. On > > any port I get: > > Error: your port uses an old layout. Please update it to match > > this bsd.port.mk. > > The ports system changed, I believe, between 4.1 and 4.2. You can > install an 'upgrade kit' - see http://www.freebsd.org/ports > > > I also have a 4.2 machine which has a working ports collection. > > (This machine I built from scratch). So I tar'd and bzip'd > > /usr/ports and sent it over to the other machine, and extracted it > > over the /usr/ports collection. I figured that as I got the ports > > collection from a working machine, it should work. But it doesn't. > > This probably would work if you rm'd or mv'd your existing /usr/ports > directory. You are actually not missing any files from the current > distribution, you have certain directories that are no longer used. In other words you had extra files, and untaring the working port tree over the old does not delete the extra files (by default). > If you simply untar the new ports collection over the old one, it > doesn't resolve the problem. Nor does cvsupping the new ports tree. Well, by default cvsup will not delete anything it does not explicitly know about. But it can be made to delete the extra stuff. So cvsupping can be made to work in this case, it just requires some extra work. If anyone wanted to know how, you could read the cvsup FAQ at: http://www.polstra.com/projects/freeware/CVSup/faq.html#adopt Basically it's more work than it's worth and you might as well delete out the non working /usr/ports and lay in the working one. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message