From: Paul Snively <psnively@mac.com>
To: Alex Baretta <alex@barettadeit.com>
Cc: "Ennals, Robert" <robert.ennals@intel.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] [OT] Rant about VCS
Date: Fri, 17 Dec 2004 12:27:12 -0800 [thread overview]
Message-ID: <08622A67-506A-11D9-9D44-000A27DEEC20@mac.com> (raw)
In-Reply-To: <41C33B0D.2090504@barettadeit.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Dec 17, 2004, at 12:01 PM, Alex Baretta wrote:
> My problem is that the project is so extensive that we use an ocaml
> program to generate the Makefiles and a bash script to appropriately
> configure findlib before anything gets done.
>
> I think we'll manage with darcs, but really I begin to understand why
> Linus went proprietary with Bitkeeper.
>
It really does sound as though you're edging from "version control"
into "configuration management." If that's the case, you may want to
look at Arch and its surrounding tools. In particular, the
documentation at
<http://www.gnu.org/software/gnu-arch/tutorial/multi-tree-
projects.html>, "Multi-tree Projects and Configuration Management,"
might be helpful to you.
Yaron Minsky pointed out that raw command-line tla can be a bit
painful, and my experience reflects that as well. OTOH, tla is very
granular, by which I mean that it's a relatively simple matter to
concoct aliases that combine tla commands/options into useful
aggregates. And I have to say that XTLA in EMACS is pretty wonderful.
> 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/>
>
Oooooh, yes, you do have a lot of complex, interrelated stuff to keep
track of. Please consider Arch.
Best regards,
Paul Snively
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (Darwin)
iEYEARECAAYFAkHDQScACgkQbot1wzHBQBVYZgCgoI3Uy5kBpsON1zFtjamRZY3q
+SgAoJaT80YqeeivliQDKsXipEv5m4vQ
=2OFB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-12-17 20:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 18:42 Ennals, Robert
2004-12-17 20:01 ` Alex Baretta
2004-12-17 20:27 ` Paul Snively [this message]
2004-12-20 8:27 ` Peter Busser
2004-12-17 20:36 ` Erik de Castro Lopo
-- strict thread matches above, loose matches on Subject: below --
2004-12-17 17:07 Alex Baretta
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-18 0:48 ` 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=08622A67-506A-11D9-9D44-000A27DEEC20@mac.com \
--to=psnively@mac.com \
--cc=alex@barettadeit.com \
--cc=caml-list@inria.fr \
--cc=robert.ennals@intel.com \
/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