From owner-freebsd-stable Mon Mar 22 13:59: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id A8D321535B for ; Mon, 22 Mar 1999 13:59:02 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 15127 invoked by uid 100); 22 Mar 1999 21:58:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 1999 21:58:22 -0000 Date: Mon, 22 Mar 1999 13:58:22 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While it's good idea, it's not the way I'd tackle it. How about grovelling over the output of "make update", and if a change in a port shows up, check /usr/ports//Makefile for the package name, and then /var/db/pkg for that name. If it's there, add a note about it to that file. Of course this misses changes in the libraries/includes/etc. that might cause you to want to rebuild a port. Date: Mon, 22 Mar 1999 13:45:43 -0800 (PST) > From: Richard J. Dawes > Reply-To: Richard Dawes > To: Mike Meyer > Cc: stable@FreeBSD.ORG > Subject: Re: Musings about tracking FreeBSD... > > Hi! > How about if you write a script that gets a list of ports you've > installed (or just ones you worry about). Then it goes through your > mail from the "cvs-all" mailing-list, and adds those regarding your list > of ports to a file (sorted to taste), discarding the rest. Run nightly, > or whenever you make world. > A quick scan of the output should indicate the ports you might > wish to upgrade. Might not be too hard in PERL. Just an idea... Good > luck! > > --Rich > > > On Mon, 22 Mar 1999, Mike Meyer wrote: > > [...] > > However, that brings up yet *another* level of problem. Even if you > > follow the correct procedures completely (or at least as completely as > > they have been specified here), you can still wind up with broken > > binaries from the /ports tree. In fact, the first time I did a system > > update, I did exactly that: update the source tree, build the world, > > install the world, build a new kernel, install the new kernel, run > > mergemaster, and reboot. Everything worked fine. Then I dumped / & > > /usr to disk and tried to burn a CD-ROM of those dumps for archival > > purposes - only to have cdrecord die in the middle with an illegal > > system call. Rebuilding cdrecord solved the problem, but this > > illustrates that the recommended procedure is incomplete - you need to > > reinstall all ports/packages as well, right? Is there a tool that > > inspects /var/db/pkg to automate that process? > > [...] > > > > > ======================================== > Richard J. Dawes rdawes@ucsd.edu > ======================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message