Larry Jones writes:
> I'm behind a firewall, too, but the point of a firewall is to keep bad
> things from happening, not to keep good things from happening. If you
> can't get some route through the firewall when you need it, then you
> have bigger problems than keeping up-to-date with the CVS sources.
[smc] Yes, bigger problems...
The company I work for (Compaq) has many tens of
thousands of employees I'm a very small cog within a very small cog
within a very big machine. Getting CVS punched through the
firewall(s) is
simply not an option for me. I suspect lots of other folks are in a
similar
position.
> Checking the source out of the repository is far and away the best
> method of keeping up -- doing an update takes a *lot* less time than
> fetching a whole new copy of the whole thing.
[smc] But it's not an option for me. (except at home, through a
slow
dialup, in which case it is _not_ faster.)
> > Can we have daily snapshots, tar-ed and gzip-ed, of the source tree?
> > I'm sure a cron job could be used to do this?
>
> Given that there's an anonymous CVS repository, there doesn't seem to be
> much point.
[smc] Might we ask, instead of "why?", "why not?". A simple script
fired up
from cron to do a cvs export then tar then gzip... how hard could it
be?
Probably harder than I imagine, for one reason or another, but
still...
>
[...]
