Brandon Metcalf wrote:
> BO => berend@cisco.com writes:
>
> BO> While we are on the subject of config specs, please allow me to ask another
> BO> question. Does anyone have a "witty" way of dealing with binary files with multiple
> BO> CPU architectures checked-in to a VOB and automatically selecting the appropriate
> BO> one based on host type? For example, let's say that you have:
> BO>
> BO> foo@@/main/SunOS/LATEST
> BO> foo@@/main/Linux/LATEST
> BO> ...
>
> This is not something you want to try to do with config specs and/or
> branches. Store binaries in a directory structure that looks something
> like /vob/tag/dir/sunos/foo or /vob/tag/dir/linux/foo and let your build
> system/makefiles do the work for you.
Sure. What you are saying applies pretty well to a software development model, but remember
that ClearCase is used for other applications as well, including hardware development where
the build process is may not lend itself that well to being Makefile driven at all steps.
It also (usually) involves many more 3rd party tools rather than a handful of compiler and
binutil programs. In addition, it pushes a whole bunch of responsibility into the users'
shell initialization files to set up the correct binary paths, etc.
I am curious as to why you are so vehemently against this idea - this works really well
with AFS.
Berend
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:51 EDT