From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,6511c3dc6e1155c9
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!proxad.net!newsfeed.stueberl.de!news2.telebyte.nl!stargate.gts.cz!newsfeed2.ip.tiscali.net!transit0.news.tiscali.nl!tiscali!transit1.news.tiscali.nl!dreader2.news.tiscali.nl!not-for-mail
Newsgroups: comp.lang.ada
Subject: Re: GWindows and David Botton
References: <s4afl0l4rv4n46ur2uqojii1s7u2du8p6e@4ax.com>
 <2004100312401227544%david@bottoncom>
 <ullenfdo8.fsf@acm.org>
 <mailman.181.1096893999.390.comp.lang.ada@ada-france.org>
 <sa4d5zy3wmn.fsf@snoopy.apana.org.au> <Pgl8d.357$Ua.154@trndny01>
 <87zn31njc6.fsf@insalien.org> <10m5opffddc6e4d@news.supernews.com>
 <87r7odnhv0.fsf@insalien.org>
 <mailman.199.1097016199.390.comp.lang.ada@ada-france.org>
From: Ludovic Brenta <ludovic.brenta@insalien.org>
Date: Thu, 07 Oct 2004 20:49:37 +0200
Message-ID: <87wty2mkhq.fsf@insalien.org>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
Cancel-Lock: sha1:EYVfyDrTgEOMA4F8Sz6DMMYdXds=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Tiscali bv
NNTP-Posting-Date: 07 Oct 2004 20:53:17 CEST
NNTP-Posting-Host: 83.134.237.32
X-Trace: 1097175197 dreader2.news.tiscali.nl 44081 83.134.237.32:37944
X-Complaints-To: abuse@tiscali.nl
Xref: g2news1.google.com comp.lang.ada:4891
Date: 2004-10-07T20:53:17+02:00
List-Id: <comp.lang.ada>

Stephen Leake writes:
> If Meta-CVS is a purely client tool, then each developer can use it
> or not; it doesn't have to be a project-wide choice.

Yes, it has to be project-wide.  The way Meta-CVS works is this:

- every file in your source tree gets a unique ID

- every file is stored in the root directory of the module in the CVS
  server under that ID

- a separate text file establishes the mapping between the unique IDs
  and the path name of each file

- when you do a "mcvs checkout module", it creates a directory
  module/MCVS under which the flat directory structure is checked out,
  then it recreates the tree using the metadata file.  It uses hard
  links if the filesystem allows that, copies otherwise.

So, using Meta-CVS instead of CVS changes the file structure of the
server.  For example:

/var/lib/cvs/my_project:
-r--r--r--  1 lbrenta src    2811 2003-08-23 20:17 F-FFA4733D2CD1E8D430F20908D38BE0DE.ads,v
-r--r--r--  1 lbrenta src   12137 2003-08-23 20:17 F-FFAE5C4ABA0AF1F53C01902609AC2355.ads,v
-r--r--r--  1 lbrenta src   41326 2003-08-31 19:48 F-FFE3C9276E16694199815F68FAF5B7C0.adb,v
-r--r--r--  1 lbrenta src    3846 2003-08-31 19:48 F-FFFE9E8E3AEE3959A23BBE6EAEE0672A.adb,v
-r--r--r--  1 lbrenta src    6135 2003-08-31 19:48 F-FFFF334EDA1C38D47B5FB63CC0CDD729.adb,v
-r--r--r--  1 lbrenta src  366052 2003-08-31 19:48 MAP,v
-r--r--r--  1 lbrenta src    3300 2003-08-31 19:48 TYPES,v

You can of course use the regular CVS client, but it's not exactly
user-friendly :)

-- 
Ludovic Brenta.