On Wed, 2007-05-30 at 15:59 -0600, Theo de Raadt wrote:
  [Jimmy Mitchener wrote:]
quoted text
> > Is there a reason snapshots do not currently come with a
> > src/sys.tar.gz as releases do?
> 
> Because every snapshot for every architecture is done on a different
> tree, and some are even done 5-6 times a day.  So this would require,
> if I can guess this right, 2.6GB per day.  Supplied over a T1.

Obviously a full tarball isn't the answer, but how about enough
information to reproduce the source code used to make the snapshot?
Something along the lines of the timestamp for the cvs update command
mentioned by Han Boetes elsewhere in the thread, plus the noncommitted
diffs, made available in an extra file or files written as part of the
automated snapshot build procedure. It seems like a problem even my
rather limited programming skills could solve, assuming I can find the
time.

While the FAQ claims there is "no significant benefit", I would think
that anything that could potentially make fixing bugs easier (especially
for code which may not be available from the CVS server) should at least
be strongly considered. It is well known in the free software community
that the more eyeballs look at source code, the more bugs get found and
fixed.

-- 
Shawn K. Quinn <skquinn@speakeasy.net>