[MITgcm-devel] Re: Package configuration

[Ed Hill]

On Tue, 2003-09-30 at 11:05, Alistair Adcroft wrote:
> We can talk about this tomorrow in our 10am meeting. When is Ralf around?
> 
> Here's a summary of discussions and suggestions for how to sort out the
> package
> configuration issue:
> 
>  o separate the package list from platform specific options
>       i.e.  gm_local (formerly .genmakerc) ->  gm_local + packages.conf
>  o gm_local can reside in source path or in ~/ /etc/ ...
>  o packages.conf should reside in the source path (i.e. ./ code/) with an order of
>    precedence and is optional (the pkg_defaults are the norm)


OK, if we switch the names then this is basically the identical
arrangement to what JMC, CNH, and I did when this setup was discussed
two months ago.  The docs at:

  http://mitgcm.org/devel_HOWTO/html_onepage/

explain that the "optfiles" (in $ROOTDIR/tools/build_options/) are
more-or-less global options for the "platform" (meaning the combo of
machine, compiler, and compiler options) being used and the "gm_local"
file is for *local* configuration information such as the set of
packages used, any locally modified files that should not be optimized,
etc.  Thats why we named it "local".

Does that make more sense?

Ed

-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Room 54-1424;  77 Massachusetts Ave.
            Cambridge, MA 02139-4307
email:   eh3 at mit.edu,  ed at eh3.com
URL:     http://web.mit.edu/eh3/
phone:   617-253-0098
fax:     617-253-4464
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://mitgcm.org/pipermail/mitgcm-devel/attachments/20030930/2b92dd8a/attachment.sig>