[M3devel] ROOT

[Tony Hosking]

I think best would be for Jay to reprise his thinking on why all of  
this was needed.  In general, I oppose hard links on the grounds that  
they are not trivially migrateable.  Better to have relative symbolic  
links.  If we can avoid the need for $origin by installing libraries  
in a fixed INSTALL_ROOT/lib directory (rather than the current  
symbolic links approach) then I prefer that.

Antony Hosking | Associate Professor | Computer Science | Purdue  
University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484




On 2 Jul 2009, at 14:31, Randy Coleburn wrote:

> I keep watching the various commit logs et al and I'm concerned too  
> that I don't readily understand what is going on and what the new  
> requirements will be going forward in terms of environment vars,  
> paths, and config file requirements, etc.
>
> As for ROOT, as an environment var, this is too generic.  If it is  
> required, it should be renamed to be specific, e.g. CM3_ROOT.
>
> Would it be possible to have a online conference about all this?
>
> Regards,
> Randy Coleburn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090702/46a29fac/attachment-0002.html>