Cyrus Harmon <ch-sbcl@...> writes:
> It's been almost two weeks since sf.net fixed their CVS problems and
> we still don't have an updated anonymous CVS tree yet. Thanks to
> Andreas Fuchs for the arch gateway, but I think this is a less-than-
> adequate long term solution. I propose that we do something about
> this situation. Options are:
> 1) continue to do nothing and hope that sf.net fixes their anonymous
> CVS mirrors
The latest word on this seems to be that it won't be re-enabled until
the end of April, at the earliest.
> 2) switch to sf.net's SVN service, which, I have heard, anecdotally,
> works better than the CVS stuff
I wouldn't be opposed to switching to SVN in this situation. In
general I don't think the benefits of SVN are compelling enough to go
through the bother of switching, but getting back anonymous access
probably is ;-)
> 3) provide a CVS mirror on cl.net.
> Personally, I'm a big fan of 3. I know that we may be trading one set
> of issues for another, but I imagine that we're going to see more
> attentiveness and response from the cl.net folks when it comes to
> resolving the inevitable problems than we are from sf.net.
This doesn't seem unreasonable, either.
> Furthermore, I'd propose moving the developer tree to sf.net as well,
> but I understand that some folks are a bit reluctant to do so and I
> understand the desire to move slowly when it comes to something like
> the "family jewels" of SBCL.
While Erik and Mario have done a great job with cl.net, I'm not sure
that cl.net has a significantly better reliability record than sf.net
for developer CVS access. There's also something to be said for not
placing all CL eggs in one basket.
> So please consider moving at least the anonymous CVS mirror, if not
> the full developer tree to cl.net. And if I'm beating a dead horse
> and there's agreement that this shouldn't happen, I'd like to know
> that. I'm also open to other options as well, should folks have any.
I don't think this has really been discussed (except once on #lisp
when the CVS outage had been going on for a few days, but IRC probably
isn't the right forum for this). Thanks for bringing up the issue.