Mike Little writes:
>
> I see postings to this mailing list and bugs-cvs indicating you and others have
>applied bug fixes
> and so on. But how is it possible to find out which bug fixes have been applied?
Use the source, Luke, particularly the ChangeLogs.
> Yes, I know I can use cvs to get all the source. But I'm behind a firewall at work,
>where I really
> want it. and if I was to get the source from home (I have done it before), I've
>still got to get it
> work (it's too big to fit on a floppy). Plus it takes a not insubstantial time to
>download and I
> have to pay for every second of my online time.
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.
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.
> 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. Many people are nervous about running interim releases, let
alone nightly snapshots. For the few people who are actively interested
in development, anonymous CVS is a much better approach.
> In fact didn't you say that the source tree is built daily on all the supported
>platforms?
Many, not all. (And not even the most popular, I'd wager, since the guy
who was running the tests on Linux stopped.)
> Surely it's not too difficult to package those binaries for each platform into a
>tarball and put
> that into the ftp directory (over-writing yesterdays snapshot would be fine).
> Ditto for the source tree.
Again, there doesn't seem to be much point; there aren't that many
people who would want them.
> Plus an online link to the changelog would be good.
There is a web interface to the anonymous CVS repository, although the
link to it got lost when SourceGear re-did the CVS web pages. It's
http://www.cyclic.com/cgi-bin/cvsweb/ccvs/.
> And some idea of current and future plans would be good.
The current plan is to fix bugs. The future is, as I'm sure you know,
very muddy -- the sale of Cyclic to SourceGear and then to OpenAvenue
has clouded by crystal ball beyond usability. Last I heard, OpenAvenue
was trying to hire someone (or someones) to run CVS -- when that
happens, I expect the fog to start to lift.
-Larry Jones
I'm crying because out there he's gone, but he's not gone inside me. -- Calvin
