Hi Sorry I've been unable to participate in the discussion, and I unfortunately won't get any time to look at for a while (we're moving city and jobs) so I won't say much because I won't be doing much for a couple of months.
Really, my only concern is that sage compiles out of the box for newbies - the fink / macports problem just keeps popping up and is IMHO an obstacle to adoption and gives a very bad first impression. I would prefer a better solution than mine, but I tend to think that mine is better than none - I would sacrifice experts' comfort. Somebody may have pointed it out, but there is an issue with the sage build system that means you can work around it by simply running 'make' a second time. D ps the relevant ticket is (from memory) probably 4130 because my patch was broken on OSX 10.4 M: +61 423 535 397 W: +61 2 6125 8260 On 07/10/2008, at 6:28, "Georg S. Weber" <[EMAIL PROTECTED]> wrote: > > > OK. > > I reopened the corresponding trac ticket #4125 (that went into Sage > 3.1.2.rc4), and asked for that patch to be reverted. > > The underlying problem might have been addressed anyway with the patch > in trac ticket #4127 (that went into Sage 3.1.3.alpha0), but Michael > Abshoff and David Philp should please have another look at the issue. > > If I can be of any help (testing, more discussion), just let me know, > I've got both a PPC Mac and an Intel Mac, the former has fink > installed on it (which is not detected by the script in question, as > it does not seem to have changed my path variable). > > 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 -~----------~----~----~----~------~----~------~--~---
