Subject: Re: CVSup collections for a NetBSD CVS tree
To: Justin T. Gibbs <email@example.com>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
Date: 04/26/1999 16:41:01
In message <199904262235.QAA84027@pluto.plutotech.com>"Justin T. Gibbs" writes
>>Not *such* a hypothetical example. Our principal Australian mirror is
>>a SPARC Classic running NetBSD! What are they supposed to do, run a
>>Solaris binary under emulation?
>Use a different, less efficient, protocol like rsync. It takes about 10
>minutes to setup rsync or cvsup on a server. If you have a whole 20
>minutes to spare, you can offer both. Why is this so hard to grasp?
Please *think* before you blurt. How many minutes does it take to set
up cvsup on a server that's a SPARC, or a mips, or a powerpc?
CVSup is not really a *solution* for *Net*BSD, until it runs on all
NetBSD platforms. ``Why is this so hard to grasp''?
Now, maybe, there are individual mirror sites which can decide to use
CVSup. But it's not a ``solution'' for NetBSD because too many users
*CANT* use it, even if they'd like to. Because it's implemented in a
second-class langauge. ``why is this so hard to grasp''?