[chora] luxor / chora

[Anil Madhavapeddy]

On Sat, Aug 11, 2001 at 04:08:20AM +0200, Cynic wrote:
> 
> Unless you decide that a separate app for each of these RC systems
> is a better solution, there's one glue inherent to all RC systems
> you might put Chora on top of: Chora itself. IOW, there's a set
> of informations Chora needs to display with any RCS on the backend.
> 
> $msg = $backend::getCommitMessage()
> 
> We don't need the same API in all supported backends, but instead
> the same API exposed by the classes interfacing those backends.
> "Hide the gory details and just give me what I want."

Concepts like RCS version numbers are pretty different across
Perforce, CVS and Subversion.

Before just diving into redesigning the API, I wanted to look
into all three and use them for a while (I havent gotten around
to looking into Subversion yet)

> I don't understand. Do you mean that with an RCS other than CVS
> it might not be possible to display e. g. diffs or something?
> Could you elaborate?

Yeah.  How do we display Subversion per-commit version numbers?
Or some of the branching functionality in Perforce in the 
history view?

> >And if we do just stick with CVS, CVSLib isn't too badly
> >broken - apart from the lack of references, it works.
> 
> I don't know what you're referring to.

If we just choose to stick Chora to CVS, what is wrong with
CVSLib apart from passing copies of CVSLib objects around?

Anil