Hmmm, things seem to tend to go the same way they went on Linux. Hopefully not.
Right now we are using CVS on our Linux Server, LinCvs on Linux-Station and
WinCvs on our Win2k-Boxes.
I really love the subversion features. A lot of them were things I missed with CVS.
Right now we are plannung to design a Java GUI. I know there are quite some
of them out there. But what I really miss with them is the clean and beautiful object
design. I have to use the command line tools to change things and interpret the
administrative files to see what happened and get the extended attributes.
Swapping over to Subversion I hoped to be able to do the same. Its true,
using a C api is niced. But using a commandline interface is more
platform independent.
What do you guys out there think about this issue?
Alex
Ben Collins-Sussman schrieb:
> Kevin Pilch-Bisson <kevin@pilch-bisson.net> writes:
>
> > Just thought I would point out cervisia, a KDE CVS gui. It is now a
> > KPart(embeddable component) as well. If no one gets to it before
> > then, I will probably look at changing it to use subversion some
> > time in August.
>
> The screenshots look beautiful, certainly nicer than the GNOME
> "pharmacy" cvs gui.
>
> But be careful: there's a lot a hand-waving going on when you talk
> about just "changing it to use subversion". CVS and Subversion have
> fundamentally different revision-control models -- like the whole
> global revision idea, for example. And properties. And branches and
> tags.
>
> And the other problem is that all current CVS guis are just wrappers
> around the command-line client, along with direct parsing of CVS/
> administrative files. Considering all the effort we've gone through
> to "librarize" subversion, it would be a *huge* disappointment to me
> if a GUI didn't use our APIs.
>
> (In fact, I think it would be downright dangerous to directly parse
> SVN/ administrative files! That's why we have a C API to access their
> contents -- the file formats should be nobody's business, and we
> should be able to change them at will, as long as the API stays the
> same.)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:32 2006