On Tue, Jul 05, 2005 at 10:42:33AM -0400, Sean Davis wrote:
> On Tue, Jul 05, 2005 at 02:07:52PM +0200, Geert Hendrickx wrote:
> > On Tue, Jul 05, 2005 at 07:33:12AM -0400, Sean Davis wrote:
> > > On Tue, Jul 05, 2005 at 12:10:59PM +0200, Geert Hendrickx wrote:
> > > > On Tue, Jul 05, 2005 at 05:43:38AM -0400, Sean Davis wrote:
> > > > > And the problem of backing up the packages if they're all going
> > > > > to be deleted prior to building so that they can be reinstalled
> > > > > if they don't build still needs to be addressed, for those of us
> > > > > who can't afford a seperate build machine.
> > > > 
> > > > pkgtools/pkg_comp makes a fine separate build machine, without
> > > > extra costs.  
> > > 
> > > Unless you consider the time required to build the release in
> > > addition to the packages a cost.
> > 
> > Simply download the tarballs.  Or if you built your own system before
> > with build.sh, do a ./build.sh release to get the tarballs for your
> > system.  
> 
> I'm well aware of how to create a release. The problem is, just like
> packages... NetBSD -current doesn't always build.

Use the tarballs of the release/snapshot you're running right now.  It did
compile, didn't it? :-)  

GH

-- 
:wq