Subject: Re: Building -current from 1.4.1?
To: NetBSD Bob <nbsdbob@weedcon1.cropsci.ncsu.edu>
From: David Brownlee <abs@netbsd.org>
List: port-vax
Date: 03/15/2000 20:56:17
On Tue, 14 Mar 2000, NetBSD Bob wrote:

> Would a more regular string of snapshots help to get this kind of situation
> fixed?
> 
	It would help, (Todd Whitesel is working on getting regular
	-current builds on about eight arches setup), but its not
	a complete fix.

> If I can speak a tad pointedwise, thinking out loud in the pipe-dream
> mode, it sure would be nice if snapshots were regular enough that even
> if there were burps in the code or builds, one could get to a recent
> build via snapshots, rather than having to build current from the last
> release.  Ideally, building current from the last release would be nice,
> but, because of the great leaps forward since 1.4.1, I sense that may
> not be quite an easy task.
> 
> How about a weekly generic snapshot with sources that built it?
> At least, for base, etc, comp, man, misc, text?
> 
	I think that is what Todd's eventual goal.

> I know, we may not have the resources, manpower, blah de blah, etc.,
> but, it would be a nice pipe-dream.
> 
> At least, all the tools, sources, and basic system would be rolled
> together at a common point in time.  It would be akin to a barebonz
> minimal system update that is known to work and be a coordinated whole.

	Another suggestion:

	How about a BUILD_README or similar in the base of the src tree -
	anytime someone makes a change that would break building from
	the last release source, they note the tool that is affected,
	and any particular gotcha. It won't catch everything (tools
	get updated for some reason, then at a later point a new feature
	is used in the build), but at least after the first person reports
	it it can get added to the file.

		David/absolute