The only problem with that is that you have to reinstall the entire =
system package.
I know it really isn't huge, but it's definitely larger than just being =
able to update
a few programs.  On a very distributed system, small updates could =
really be a lifesaver.

And do you really feel safe reinstalling base.tgz on your production =
boxes
whenver a security advisory comes out?  ;)

-----Original Message-----
From: Julio Merino [mailto:jmmv@menta.net]
Sent: Monday, February 24, 2003 11:23 AM
To: Sporleder, Matthew (CCI-Atlanta)
Cc: current-users@netbsd.org
Subject: Re: build.sh feature request


On Mon, 24 Feb 2003 11:00:06 -0500
"Sporleder, Matthew (CCI-Atlanta)" <Matthew.Sporleder@cox.com> wrote:

> That handles the system upgrade process.
> Thanks,
> How about the patch-type updates?  :)

Theorically syspkg helps in this. Suppose a security advisory is =
published.
We could release together with it new versions of the syspkg's that were
affected by the problems. You could simply update the packages broken.

Well, I have not much idea on how this (will) works.

--=20
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/