[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Client CVS implementations ( was : Re: XML interface to cvs )

From: Rob Helmer
Subject: Re: Client CVS implementations ( was : Re: XML interface to cvs )
Date: Wed, 27 Mar 2002 12:44:23 -0800
User-agent: Mutt/1.2.5i

Hi Oliver,

Yes, a libCVS would be nice. A google search on "libcvs" turns
up some interesting results, there might be a nice starting point

I am seriously considering implementing an abstracted version
of the client/server protocol in Perl, I was sent a perl module that
already does a few of the functions ( I sent a private email
to James Richardson regarding an old post in the CVS archives,
he sent me what he developed ).

The client implementation currently doesn't deal with meta-data
directories, but once that is in and the client/server implementation
is complete in the module I *think* it should be perfect for the
project I am working on ( since SandWeb is a CGI, I'd rather have
it live completely in Perl than to make calls to external programs.
There are *alot* of pros/cons to this approach, the #1 thing I
don't like is not reusing available Unix programs like SSH and
CVS. I do think that it makes a more consistent, multi-platform
choice to go pure OO Perl though, and any modules we come up
with can be reused easily on CPAN ).

However, this is probably a long term sub-project, and thanks to
other members of the list we will probably use some expect/ssh/cvs
hackery to get SSH support for SandWeb in the short term.

Rob Helmer

On Wed, Mar 27, 2002 at 08:56:24PM +0100, Oliver Fischer wrote:
> --
> Oliver Fischer - mailto:address@hidden
> > Does anyone know of any implementations of the CVS client part of
> > the client/server protocol in Perl, Python, C ( besides the CVS binary :)
> > Ruby, etc. ? Java is nice, but since the core application is not
> > running in a VM and it's mostly stateless between executions, I
> > don't see an advantage to using the Java implementation.
> I am writting a moment a perl wrapper too.... yacvswrapper... ;)
> > AFAIK, the "official" CVS doesn't have the various functions split
> > into a library, it's all implemented in the binary, right? ( I've browsed
> > the source, I obviously haven't read it since I'm asking this ).
> Unfortunately cvs is a monolithic binary. I thought about a native perl
> binding, but I discarded the idee after looking at the sources. To have a
> libCVS with a nice and extendsible API would be something great and give CVS
> a new boost.
> Bye
> Oliver
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]