[M3devel] HEADS UP: cm3.cfg locations, was: Re: problems with cm3.cfg and MxConfig

[Jay K]

Correct. cm3 could probe for exceedingly few places, and those could then include whatever they want.
Like how I moved everything to config, except the initial cm3.cfg (but then ran afoul briefly of my own INSTALL_ROOT = function of path() approach)
 
Of course there is the tension of this being user editable or not, and therefore having to put every probe in on the theory that it isn't user editable.
 
  - Jay


----------------------------------------
> Date: Mon, 3 Aug 2009 17:49:02 -0400
> From: hendrik at topoi.pooq.com
> To: m3devel at elegosoft.com
> Subject: Re: [M3devel] HEADS UP: cm3.cfg locations, was: Re: problems with cm3.cfg and MxConfig
>
> One could have the configuration file contain the locations where to
> find other configuration file(s). The file names in tis file could have
> explicit notations indicating "where the compiler is", "current
> directory", "User's home directory", "check the environment variable",
> and so forth.
>
> This would make things somewhat more flexible, It's not clear whether
> the added complexity would get in our way.
>
> -- hendrik