Snapshots src/sys tarballs

Is there a reason snapshots do not currently come with a
src/sys.tar.gz as releases do? I would think this to be
quite useful
for people wishing/requiring building their own kernels, and
using
snapshots, as it would help to minimize damage from
kernel/userland
(and packages) coming out of sync.

I'm sure there's a good reason for them not being included,
but I'm
just curious as to what it is, I was unable to find anything
in the
archives.

Jimmy.

On 2007/05/30 09:51, Jimmy Mitchener wrote:
> Is there a reason snapshots do not currently come with
a
> src/sys.tar.gz as releases do? I would think this to be
quite useful
> for people wishing/requiring building their own
kernels, and using
> snapshots, as it would help to minimize damage from
kernel/userland
> (and packages) coming out of sync.

if you follow development code, you should really be able to
work
without such hand holding (-: reading source-changes helps
avoid
problems, cvs up -D [date] can help if you bump into
something and
need older code.

anyway, snapshots aren't always quite the same as you get
from
-current source.

> anyway, snapshots aren't always quite the same as you
get from
> -current source.

That's my point really. I would think it to be advantageous
to have a
snapshot of the code just as that snapshot was created (no
pun
intended). But yes, you could avoid the pitfalls I
described
previously by following source-changes. I was just curious
as to why
it wasn't included as it is for releases.

On Wed, May 30, 2007 at 10:26:09AM -0800, Jimmy Mitchener
wrote:
> >anyway, snapshots aren't always quite the same as
you get from
> >-current source.
> 
> That's my point really. I would think it to be
advantageous to have a
> snapshot of the code just as that snapshot was created
(no pun
> intended). But yes, you could avoid the pitfalls I
described
> previously by following source-changes. I was just
curious as to why
> it wasn't included as it is for releases.

Here's what *I* think (fwiw) snapshots are about, in no
particular
order...

 - Snaps serve as a starting point if you *really* want to
follow
   -current (as in compiling latest stuff in the tree,
testing patches,
   etc).

 - Snaps are an easy way to *kinda* follow -current without
following
   -current. 

Here's what *I* think snapshots are NOT...

 - Mini -release, with all the goodies you've come to expect
from
   *real* releases.

-- 
Darrin Chandler            |  Phoenix BSD User Group  | 
MetaBUG
dwchandlerstilyagin.com   |  http://phxbug.org/      |  http://metabug.org/
http://www.stilyagin.com/  |  Daemons in the Desert   |  Global BUG Federation

Jimmy Mitchener wrote on Wed, May 30, 2007 at 09:51:02AM
-0800:

> Is there a reason snapshots do not currently come with
a
> src/sys.tar.gz as releases do? I would think this to be
quite useful
> for people wishing/requiring building their own
kernels, and using
> snapshots, as it would help to minimize damage from
kernel/userland
> (and packages) coming out of sync.
> 
> I'm sure there's a good reason for them not being
included, but I'm
> just curious as to what it is, I was unable to find
anything in the
> archives.

http://w
ww.openbsd.org/faq/faq5.html#Flavors

:: It is sometimes asked if there is any way to get a copy
of exactly
:: the code used to build a snapshot.  The answer is no. 
First, there
:: is no significant benefit to this.  Second, the snapshots
are built
:: as desired, as time permits, and as resources become
available.
:: On fast platforms, several snapshots may be released in
one day.
:: On slower platforms, it may take a week or more to build
a snapshot.
:: Providing tags or markers in the source tree for each
snapshot would
:: be quite impractical.

Besides, snapshots often contain uncommitted tweaks, so a
cvs tag
would not even do the job for you.

Ingo Schwarze wrote:
> Besides, snapshots often contain uncommitted tweaks, so
a cvs
> tag would not even do the job for you.

Perhaps a timestamp of the exact moment the build started so
you
can.

  cvs -qz3 update -D 'timestamp'

To get exactly the same source. I don't know well this is
possible, but it sounds like an idea.



# Han

On 2007/05/30 21:47, Han Boetes wrote:
> Ingo Schwarze wrote:
> > Besides, snapshots often contain uncommitted
tweaks, so a cvs
> > tag would not even do the job for you.
> 
> Perhaps a timestamp of the exact moment the build
started so you
> can.
> 
>   cvs -qz3 update -D 'timestamp'
> 
> To get exactly the same source.

ever noticed something like 'in snapshots for a week'
mentioned in
a commit log?

Stuart Henderson wrote:
> On 2007/05/30 21:47, Han Boetes wrote:
> > Perhaps a timestamp of the exact moment the build
started so
> > you can.
> >
> >   cvs -qz3 update -D 'timestamp'
> >
> > To get exactly the same source.
>
> ever noticed something like 'in snapshots for a week'
mentioned
> in a commit log?

I can't say I have, nor that I can easily find it in the
archives. Pray enlighten me.


# Han

> 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.

Keep dreaming though.

On 2007/05/30 23:53, Han Boetes wrote:
> Stuart Henderson wrote:
> > On 2007/05/30 21:47, Han Boetes wrote:
> > > Perhaps a timestamp of the exact moment the
build started so
> > > you can.
> > >
> > >   cvs -qz3 update -D 'timestamp'
> > >
> > > To get exactly the same source.
> >
> > ever noticed something like 'in snapshots for a
week' mentioned
> > in a commit log?
> 
> I can't say I have, nor that I can easily find it in
the
> archives. Pray enlighten me.

s/snapshots/snaps/ then:

http://marc.info/?l=openbsd-cvs&m=1180108807273
43&w=2
http://marc.info/?l=openbsd-cvs&m=1180110515230
08&w=2
http://marc.info/?l=openbsd-cvs&m=1170198447318
12&w=2
http://marc.info/?l=openbsd-cvs&m=1168308964229
23&w=2
http://marc.info/?l=openbsd-cvs&m=1165153395044
42&w=2

etc.