From owner-freebsd-questions Tue Nov 16 9:49: 2 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ns.clientlogic.com (ns.clientlogic.com [207.51.66.75]) by hub.freebsd.org (Postfix) with ESMTP id 0583F14D2B for ; Tue, 16 Nov 1999 09:48:43 -0800 (PST) (envelope-from ChrisMic@clientlogic.com) Received: by site0s1 with Internet Mail Service (5.5.2650.21) id ; Tue, 16 Nov 1999 12:48:48 -0500 Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105D82@site2s1> From: Christopher Michaels To: "'rjk191@psu.edu'" , jcm@dogma.freebsd-uk.eu.org Cc: freebsd-questions@FreeBSD.ORG Subject: RE: re-compiling ports after cvsup Date: Tue, 16 Nov 1999 12:52:11 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Ray Kohler [SMTP:ray@psu.edu] > Sent: Monday, November 15, 1999 12:40 AM > To: jcm@dogma.freebsd-uk.eu.org > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: re-compiling ports after cvsup > > On 15 Nov, Jonathon McKitrick wrote: > > Is there one command that will rebuild ALL the ports without installing > > them? Something similar to 'make buildworld', only for the ports > > collection? > > Go to the top level of the ports collection (/usr/ports) and run "make" > with no arguments. This will build all of them without installing them > also. The handbook has a good deal on this. > Woah, that'll make ALL of the ports, not just the ones you have installed. I hope you have several gig to burn on that partition. The distfiles alone will be over 1.7GB. > > Also, when trying the new version of a port, even though > > the package may have a different name, won't the binary have the same > > name and overwrite the older version? > > Yes, but the idea is to try the new version in the build directory > (without installing it). Don't run make install until you think it's a > good idea. > Yes you can do this. But it'll add clutter in several ways. #1) /var/pkg will get full of information on all the old and new versions, and it can become confusing to, say the least. #2) What if a new version of a program doesn't have the exact same packing list. You'll end up having old files from old versions hanging around your system, taking up space and causing confusion as well. Binaries aren't always the only thing installed with a port. There can be config files, documentation, libraries, etc... Unfortunately there is no equivalent to "make buildworld" for _just_ the ports you have installed. Has anyone pointed out the pkg_version, in the ports collection? It goes through the list of installed ports, and the list of available ports in /usr/ports and tells you which ones need updating. -Chris > -- > Ray Kohler > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message