The main things I see that marion needs are:
1) making it use a single diff algorithm which allowed
versions to be automatically reconstructed from deltas.
This could probably be done using GNU diff and GNU patch.
2) Some support for branching / merging, other than just
making a copy of the DB.

Number one should be pretty easy. Number two is sort of
nebulous, and could be either moderatly easy or a lifetime
project ;-).

I kind of agree with the comment from Doug Chamberlin
about re-inventing the wheel, but on the other hand, open
source can scale in strange ways. If there are people interested
in the source control system who would not contribute much
to the product, than having them work on the the SCS is not
really a loss. It's a gain if they make a system better than
the one that would be used otherwise.

I'm not voting for or against using marion at this
point. Just trying to add some data.

> Date: Tue, 25 Jan 2000 16:31:11 -0500
> From: Dalton Calford <dcalford@...>
> Subject: Re: source control - marion etc
>
> Hi Reed,
>
> How much work do you think there would be to update Marion?
> Since you have intimate knowledge of Marion and what is lacking in it, would you
> be willing to list the development projects needed to make it more suitable? (or
> even become a team leader for such a project if the source for Marion also
> becomes available)
> I would be willing to commit time and money towards such a project, if it looks
> feasible and the community shows an interest in using it.
>
> best regards
>
> Dalton
>

_________________________________________________________
Get your own FREE portalofevil.com Email account at...
http://www.portalofevil.com

PortalofEvil.com - Websites by the insane for the insane.
_________________________________________________________