[M3devel] cm3.cfg for Windows

[jay.krell at cornell.edu]

They are both valid. The larger one makes some guesses and delegates  
back to the cvs tree. It is nice for when you are actively editing the  
files and don't want to also copy them. It also will delegate to the  
installed ones and there its value is honoring the CM3_TARGET  
environment variable.

Upgrade.py should probably have a command line option.

Really upgrade is just a LITTLE more than do-pkg and might need some  
rethinking. It also copies cm3 for example which is really a  
workaround for cm3 not shipping itself.

For you probably the two liner.

  - Jay (phone)

On Sep 2, 2009, at 3:46 PM, "Randy Coleburn" <rcoleburn at scires.com>  
wrote:

> Jay:
>
> After running your "upgrade.py" I notice that the "cm3\bin\cm3.cfg"  
> file has been replaced and now contains 134 lines instead of the 2  
> lines you had described earlier.
>
> Let me know if I should switch back to the 2-line variant you  
> described earlier, or if the new 134-line file is the new way forward.
>
> Regards,
> Randy