Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alex Baretta <alex@barettadeit.com>
To: Ocaml <caml-list@inria.fr>
Subject: [OT] Rant about VCS
Date: Fri, 17 Dec 2004 18:07:54 +0100	[thread overview]
Message-ID: <41C3126A.3060101@barettadeit.com> (raw)

Please forgive me for ranting about source code Version Control Systems 
on the list, but I can't help it. Besides, I would like to know what the 
gurus on the list use to manage their own projects.

My company handles close to 100kloc of Ocaml and ocaml related files 
under CVS. We have gotten sick and tired of having to reconstruct CVS 
repositories from scratch every once in a while because we need to move 
files or delete directories.

It appeared to us that Darcs might solve the problem: it seems based on 
a reasonably sound algebraic model and is written in Haskell, which 
supposedly should be a bonus compared to other VCSs written in C.

Yet, darcs lacks some of the most basic features of a VCS, such as 
handling metadata (the executable bit, essentially). The darcs 
developers say that this is a "planned feature" but nothing really 
urgent. Actually, we think this is a critical feature in a big project 
which relies on scripts and other executables distributed together with 
the source for bootstrapping purposes. Ocaml itself ships with a full 
compiler to be able to bootstrap, albeit this does not depend on the 
executable bit being set anywhere since ocamlrun is generated by the C 
compiler.

Other VCSs such as subversion seem to be so unstable as to severely 
discourage their use in an industrial project.

***

What is the Ocaml way to solve this problem? What VCS do caml breeders 
and riders use?

I definitely hope I must not write YAVCS in Ocaml...

Alex

-- 
*********************************************************************
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL

tel. +39 02 370 111 55
fax. +39 02 370 111 54

Our technology:

The Application System/Xcaml (AS/Xcaml)
<http://www.asxcaml.org/>

The FreerP Project
<http://www.freerp.org/>


             reply	other threads:[~2004-12-17 17:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 17:07 Alex Baretta [this message]
2004-12-17 18:42 ` [Caml-list] " Paul Snively
2004-12-17 19:28   ` Yaron Minsky
2004-12-17 20:13   ` Erik de Castro Lopo
2004-12-17 21:37 ` Sven Luther
2004-12-17 22:27   ` Erik de Castro Lopo
2004-12-18  9:28     ` Sven Luther
2004-12-18  9:49       ` Erik de Castro Lopo
2004-12-18 14:45         ` Sven Luther
2004-12-18 20:03           ` Erik de Castro Lopo
2004-12-18  9:52       ` Erik de Castro Lopo
2004-12-18 14:45         ` Sven Luther
2004-12-18 11:24       ` Richard Jones
2004-12-18 15:01         ` Sven Luther
2004-12-18 15:22           ` Richard W.M. Jones
2004-12-18 15:35             ` Richard W.M. Jones
2004-12-18 15:39             ` Sven Luther
2004-12-21  9:07     ` [Caml-list] [OT] Rant about VCS: Conclusions Alex Baretta
2004-12-21 22:03       ` Blair Zajac
2004-12-21 22:36         ` Erik de Castro Lopo
2004-12-21 23:19           ` David Brown
2004-12-21 23:47             ` Erik de Castro Lopo
2004-12-18  0:48 ` [Caml-list] [OT] Rant about VCS skaller
2004-12-18 11:25 ` henri dubois-ferriere
2004-12-18 15:03   ` Sven Luther

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41C3126A.3060101@barettadeit.com \
    --to=alex@barettadeit.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox