Its called "variation control"..Use Clearcase or any source code control
system
for "version control" not for "variation control". Use Makefile for the
"variation control".
Guna...
While we are on the subject of config specs, please allow me to ask another
question. Does anyone have a "witty" way of dealing with binary files with
multiple
CPU architectures checked-in to a VOB and automatically selecting the
appropriate
one based on host type? For example, let's say that you have:
foo@@/main/SunOS/LATEST
foo@@/main/Linux/LATEST
...
Could one construct a config spec to automatically select the correct binary
for the
current host (kind of like the way AFS' @sys path element works, if anyone's
familiar with that)?
It seems impossible without introducing an architecture type or environment
variable
function into ClearCase's config spec query language, but I'd be curious to
hear if
people have other ideas.
Berend
P.S.: Yes, I know that it may, in most cases, be more preferable to only
check-in
sources and not binary object, but there are times when 3rd party tools are
involved
or the same view needs to be active on machines of different architectures
where
such an approach would not be possible or work properly.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:51 EDT