[Top][All Lists]

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

Re: Providing the functionality of CVS as a library

From: Rob Helmer
Subject: Re: Providing the functionality of CVS as a library
Date: Sun, 3 Nov 2002 22:31:15 -0800
User-agent: Mutt/1.2.5i

On Mon, Nov 04, 2002 at 12:08:01AM -0500, Alex Taler wrote:
> >>>>> "Rob" == Rob Helmer <address@hidden> writes:
>   Rob> We looked at VCS::Cvs for inclusion into SandWeb, and realized the same
>   Rob> thing, so we wrote our own abstracted Perl CVS class (
>   Rob> SandWeb::Repository::cvs ).
>   Rob> If you want to check it out, I'd reccommend getting the CVS version -
>   Rob>
> Thanks, I took a look at it.  It doesn't look quite like what I
> want.  I am thinking of an API in which the managed CVS files are
> individual objects which you can manipulate.  Along the same
> lines as in VCS::Cvs.  The benefit I see to this approach is
> better handling of unusual cases.  How do you handle error and
> unusual cases?

Hi Alex,

Handling managed files as objects is a pretty cool idea conceptually,
if you end up doing this let me know as I may be interested in
collaborating ( SandWeb is going to use what you see there for the
1.0 release, after that who knows? ).

Repository::cvs is really just a wrapper around the cvs command
line utility, say you create a $repository object using R:c's 
constructor, then call it's methods ( which are for the most
part one-to-one to the CVS commands ). You pass the filename
or directory you wish to work with in the constructor.

There is a seperate SandWeb::File object which we use to manupulate
files, I think the concept could be extended to SandWeb::Repository
as well.

Anyway, in the case of CVS we generally handle errors based on
the error level that the CVS binary leaves.


reply via email to

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