Subject: Re: binary for NetBSD Security Advisory 2003-009: sendmail
To: None <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 04/08/2003 14:39:05
[ On Monday, April 7, 2003 at 22:22:41 (-0400), David Maxwell wrote: ]
> Subject: Re: binary for NetBSD Security Advisory 2003-009: sendmail
> I'm curious how you've gone about building the lists of files that need
> to be updated - anything automated, or do you do it all manually?
FYI, what I do right now is entirely manual. I make the fixes on a
development system, install and test and so on. Then I do a "make
install" in the appropriate sub-directories on the prototype machine,
cut&paste the output to edit out a list of updated files, and I tar them
up and put them in my patches sub-directory. (My source trees are NFS
mounted on the prototype machine from the development system and each
system has its own local object directories, so the "make install"
hopefully just rebuilds what needs to be rebuilt.)
This process is onerous enough that I only build patches for stuff that
might actually pose a real risk to my clients.
I'm hoping that with future releases I might be able to leaverage a bit
off the new meta-log mechanisms in "install"....
Greg A. Woods
+1 416 218-0098; <firstname.lastname@example.org>; <email@example.com>
Planix, Inc. <firstname.lastname@example.org>; VE3TCP; Secrets of the Weird <email@example.com>