On Sun, 6 Oct 2002, Larry McVoy wrote:
> If we GPL it or we allow clones, all that does is stop the development.
> It's not a question of is there the ability in the community to do what
> we do, there certainly is. It's a question of will they. And the answer
> is no they won't or they would have already.
As usual, I agree with this point and think it's worth highlighting.
The GPL fanatics can flame me all they want, but that's not going
to change the reality. The only thing that _will_ change the
situation is a team of people getting together to develop a GPL
alternative to bitkeeper.
Subversion isn't it, we can't work from the same repository with
tens of thousands of people, any BK replacement would have to be
a distributed system.
PRCS2 might become a suitable system, if somebody gets around to
picking up its development. Arch might work too, but I remember
talking to some Arch fans a while back who "were about to" import
the whole kernel history into an Arch repository ... the fact
that I never heard from them again makes it look like maybe Arch
couldn't yet handle a repository the size of the kernel.
In short, until somebody builds a free (as in RMS-free) source
control system that's as good as bitkeeper for what the kernel
needs, bitkeeper is the only available tool for the job.
If you (for random values of you) care enough about bitkeeper
not being free, you should probably implement something as good
as, or better, than bitkeeper ;)
regards,
Rik
-- Bravely reimplemented by the knights who say "NIH".http://www.surriel.com/ http://distro.conectiva.com/
Spamtraps of the month: september@surriel.com trac@trac.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:55 EST