source file organization

[Matthias Andree]

David Relson <relson at osagesoftware.com> writes:

> Using SourceForge for cvs services restricts us to what the cvs commands
> let us do.  If we could do as you suggest, there wouldn't be a problem.
> However, moving files is outside the cvs command set and we don't have
> the needed access on SourceForge.  Unless I'm missing an important
> detail, which is always possible, we can't do as you suggest.  I wish we
> could, but I don't think we can.  Darn :-(

I had a glance at mcvs (Meta-CVS) 1.0 recently, which claims to embrace
and extend cvs, and version the structure changes (i. e. file renames),
but I'm not aware of how stable it is already. It looks as though it was
a pure client-side install, in that all of us developers would just
install Meta-CVS and off we went. The drawbacks are clear: 1. each of us
would need to install CLISP (GNU common lisp) 2.30 or newer, which
doesn't work with gcc-3.2, but requires gcc-2.95.3 (tried it with 3.2,
it failed, SuSE don't ship gcc-2.95.3...), 2. each of us would need to
install mcvs (again), 3. SourceForges's ViewCVS would fall over,
4. every simple operation such as status or diff or update or
you-name-it prints utterly unreadable file names, you need to filter
everything through mcvs filter (mcvs fi) to get readable file names with
paths.

Example ViewCVS: http://m2a2.dyndns.org/cgi-bin/viewcvs.cgi/mcvstry/

Ugly, no? :-}

-- 
Matthias Andree