From owner-freebsd-ports Fri Jul 30 0:46:12 1999 Delivered-To: freebsd-ports@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 0E69B1508B for ; Fri, 30 Jul 1999 00:46:09 -0700 (PDT) (envelope-from will@shadow.blackdawn.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=shadow.blackdawn.com) by neptune.psn.net with esmtp (PSN Internet Service 2.12 #3) for freebsd-ports@FreeBSD.ORG id 11A7Ky-0000wi-00; Fri, 30 Jul 1999 00:44:18 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.2) id DAA72248 for freebsd-ports@FreeBSD.ORG; Fri, 30 Jul 1999 03:44:12 -0400 (EDT) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990730032920.A17314@semiotek.com> Date: Fri, 30 Jul 1999 03:44:11 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: freebsd-ports@FreeBSD.ORG Subject: RE: Can I automatically upgrade a large number of ports? Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Jul-99 Justin Wells wrote: > > I first posted this to freebsd-questions, but nobody there seemed to > know the answer. There is none (yet) that I know of. > Boy this is tedious. > > I would like to issue a single command that goes off and grabs the > newest ports, finds out what I have installed that is now obsolete, > and upgrades just those packages. If it can't do every single package > well ok--if it can do the majority that would be great (I know > pkg_version doesn't accurately assess everything, but it gets most > of it right). It's one area of the ports collection that I'd sure like to polish, as well as (I'm sure) other porters/contributors. If you'd like to do the job.. go for it! > I tried writing a script to do this, based on pkg_version, but it > turned out to be dangerous and difficult: > > -- I don't want to pkg_delete until I know that I've got the > new version all compiled and configured; otherwise I might > wipe out something important. pkg_delete complains anyway if > I try to do this > > -- If I don't run pkg_delete then I get multiple versions of the > same port installed, one over the other. The package database > gets all messed up, and worse yet, pkg_version stops reporting > useful information about that port (too many versions installed). Instead of running pkg_delete first, simply make the new version of the port, test it out, then pkg_delete, and install the new version. I'm sure it'd be tedious, if you like updating your programs on a regular basis. I just update them whenever I find it necessary (i.e., update a version of a program that I want, only to find out it wants a new version of this or that library...) > -- It's tricky relating a package name back to a directory in > /usr/ports. Are they guaranteed to be unique? Can I do a > cd /usr/ports/*/rsync and be sure there will never, ever > be a /usr/ports/games/rsync as well as the one I want? I wouldn't try this. I don't think there are any categories with ports of the same name at this time, but there may be in the future. -- Will Andrews System Administrator, Gatekeeper Technologies http://www.gatekeep.net/ - Powered by FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message