> > > The workaround for you is pretty simple, though it will take a few > > > hours of sleep for it to happen. > > > > 1) Download the *source* to Sage, e.g. > > > athttp://www.sagemath.org/download-source.html > > > 2) Follow the instructions to build Sage from source. It consists of > > > going into a certain directory in Terminal and typing "make". > > > 3) Wait a few hours. > > > 4) Now try to install your package! > > Seems like overkill if R is the only package that stores paths a build > time. >
You're right, but not everyone understands what 'replacing bad paths' is - it's a tricky business, at least for me. These are instructions that don't require a lot of background. The real problem is that "R's spkg-install is a mess", as one Trac ticket says. Probably somewhere in there lies the answer to not hard- coding these things. But it will take a lot of work by someone who knows R and Sage's build process to fix that. Please feel free to try! We'd love the help; R is a very important part of Sage which is underutilized right now. - kcrisman -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
