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-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,bed15592664c9bfd
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-06-05 07:33:31 PST
From: "Martin Dowie" <martin.dowie@nospam.baesystems.com>
Newsgroups: comp.lang.ada
References: <mailman.1023277322.25539.comp.lang.ada@ada.eu.org>
 <slrnafs1g8.aa1.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <3cfe0e86@pull.gecm.com>
 <slrnafs562.aa1.randhol+abuse@kiuk0152.chembio.ntnu.no>
Subject: +Re: Can any body clarify me !!
Date: Wed, 5 Jun 2002 15:37:29 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
NNTP-Posting-Host: sg2c11210.sd.edinbr.gmav.gecm.com
Message-ID: <3cfe2133$1@pull.gecm.com>
X-Trace: pull.gecm.com 1023287603 sg2c11210.sd.edinbr.gmav.gecm.com (5 Jun
 2002 15:33:23 +0100)
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!btnet-peer!btnet-peer0!btnet-feed5!btnet!newreader.ukcore.bt.net!pull.gecm.com!not-for-mail
Xref: archiver1.google.com comp.lang.ada:25359
Date: 2002-06-05T15:37:29+01:00
List-Id: <comp.lang.ada>

"Preben Randhol" <randhol+abuse@pvv.org> wrote in message
news:slrnafs562.aa1.randhol+abuse@kiuk0152.chembio.ntnu.no...
> On Wed, 5 Jun 2002 14:17:47 +0100, Martin Dowie wrote:
> > "Preben Randhol" <randhol+abuse@pvv.org> wrote in message
> > news:slrnafs1g8.aa1.randhol+abuse@kiuk0152.chembio.ntnu.no...
> > [snip]
> >> Why would you want to do that? It sounds to me that you will only have
> >> more problems editing your files this way.
> >
> > One 'real' target version, one 'fake' host version, test stub versions
etc.
>
> Then I would recommend using CVS

Well, you could but I usually like having all version hanging around
in a:

<project root>
  + <csci1 name>
  |   + <csc1 name>
  |   |   + spec
  |   |   + host
  |   |   |  + build
  |   |   |  + test
  |   |   + target1
  |   |   |  + build
  |   |   |  + test
  |   |   + target2
  |   |      + build
  |   |      + test
  |   + <csc2 name>
  + <csci2 name>
    etc

still directory structure with the same structure within the
config system. If target1 and target2 share a body I can always
'link' them together with the config tool (never found a config
tool that didn't have this, yet...)

Each to there own...