Hi, it is relatively easy to include workarounds in the script machinery, and for DYLD_LIBRARY_PATH this should already be the case.
The difficult thing is to test, whether the problems users report every now and then do really disappear. It seems that none of the Sage developers has had these problems on a machine on his own (including myself). There only are these bug reports 1."Sage does not build" 2. More or less dicussion 3. "Hey, try to move macports out of the way" 4. "Now it builds, thank you!" But I do not know how to produce "out of the box"a kind of doctest for this, ensuring that a potential fix really is a working fix. Cheers, gsw --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
