The hard-coded directory currently breaks "sage --upgrade" if the install directory has been moved. It fails on opencdk-0.6.6.p4 .
--walter On Jun 11, 8:09 am, leif <not.rea...@online.de> wrote: > On 11 Jun., 08:43, Jason Grout <jason-s...@creativetrax.com> wrote: > > > > > > On 06/10/2010 04:49 PM, Jason Grout wrote: > > >> There seem to be a lot of loose ends left hanging when asagedirectory > > >> is moved. For example, I usually compileSageon a ramdisk, and then > > >> move it to my home directory. > > > > [snip] > > > >> It seems common knowledge inSagethat you can compileSageand move the > > >> directory around to your heart's content. Maybe we should put a warning > > >> somewhere cautioning people that there are lot of packages included in > > >>Sage, andSagemight not automatically change the right directory > > >> information for every package? > > > >> This seems like a goldmine for possible subtle bugs... > > > Seehttp://trac.sagemath.org/sage_trac/ticket/9210foran updated > >sage-location script which takes care of the problems with pkg-config if > > the build directory moves. This should take care of the matplotlib > > freetype problems from a recent thread if the build directory is moved > > (the fix on #9208 only works if the build directory hasn't been moved). > > > See alsohttp://trac.sagemath.org/sage_trac/ticket/5776, where mabshoff > > filed a ticket for these kinds of things over a year ago. > > At least the hardcoded paths in binaries are a "known" issue... ;-) > > They do not necessarily breakSageaftermoving, but can be a security > issue (not really addressed yet). > This also affects binary dists (depending on where they have been > built). > > -Leif -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
