Hi On 4 February 2016 at 13:42, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2016-02-04 12:32, Jan Groenewald wrote: > >> Is there any plan to support this in future? >> > I don't think so. This used to be semi-supported in the past (before Sage > 7.0), but it is too difficult to do correctly. > I'm under the impression almost all software works relocatable, and only start off hardcoded due to time pressure, but then get fixed. Is it difficult because of legacy code? Does it matter for the PPA? Isn't that installed in a fixed location anyway? Yes, changes to this it is what broke the PPA since 6.9. I didn't catch it between dev and stable because I run the -full version. My head explodes that sage patches binaries after compilation to fix hardcoded paths. If I google "hardcoded paths" then there are mainly results about how to fix having hardcoded paths. I don't know which parts of Sage or packages in Sage do not support prefixes. It seems bizarre. Are there just not enough people working on the build side of Sage? Does most of the sub-packages not support prefixes? Regards, Jan > > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-support@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. > -- .~. /V\ Jan Groenewald /( )\ www.aims.ac.za ^^-^^ -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
