Re: gcc-ss-20011119 is now available

["David O'Brien" <obrien at FreeBSD dot org>]

On Wed, Nov 21, 2001 at 04:37:11PM -0500, Phil Edwards wrote:
> On Wed, Nov 21, 2001 at 11:43:33AM -0800, David O'Brien wrote:
> > On Wed, Nov 21, 2001 at 07:31:06PM +0000, Joseph S. Myers wrote:
> > > You can always
> > > tag and build and distribute your own tarballs using the gcc_release
> > > script.
> > 
> > That is more effort than I am willing to put into this with all the other
> > open source things I do.  Especially when the frame work for making GCC
> > snapshots is alreadly [mostly] in place.
> 
> That sounds contradictory.  The framework for making GCC snapshots is
> already mostly in place... so why can't you use it?  

So is the framework to build a FreeBSD release.  But 99% of the people
prefer snapshots over being told to roll their own.

I am a FreeBSD developer 1st, and a GCC developer 2nd.  So that is how my
time is split.  We've seen in the FreeBSD community a great use in
providing daily snapshots of our release branch (at releng4.freebsd.org)
and mainline (current.freebsd.org).  If you want to get your bits in more
people's hands easier, snapshots are the way to go.

BTW, both of these snapshot machines are co-located at large FreeBSD
user's site; and the use of the machines were given for what ever purpose
we saw fit.

Aren't there contact with-in the GCC community that provides the same?

> What do you need done that gcc_release doesn't do?

I have to configure the cron job, ensure suffient disk space, check the
build logs, ftp the tarballs to some larger site other than my DSL line,
etc...  I have found that when already doing this for one branch
(FreeBSD) it isn't that much additional work give care and feeding to a
2nd branch.  BUT to start doing that initial work does take a much larger
care and feeding.

It was just a suggestion that would make life easier for your users.

-- 
-- David  (obrien@FreeBSD.org)