[M3devel] M3Config

[Olaf Wagner]

Quoting Jay K <jay.krell at cornell.edu>:

> So..I was wondering..what were the original authors thinking?
>
> And there was that comment about the file containing the data upon install.
>
> Which seemed wrong to me.
>
> They were probably thinking of the way 3.6 was packaged and   
> distributed -- everyone built the system from source, upon building   
> m3build/m3ship from C and m3 from assembly.
>
> That isn't a bad model, but we probably want both.
>
> There are at least three times the paths can be computed/recorded:
>
>   1) when you build libm3
>   2) when you install libm3
>   #1 and #2 may or may not be close in time and have the same result.
>   3) by parsing cm3.cfg as needed
>
> #2 is more efficient than #3 and matches the old code, but #3 is how  
>  I left it, probably ok.

I'd prefer that, too. I take it that you've changed the code correspondingly
and we should move the RC2 tag?

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194