On Friday, March 18, 2016 at 12:04:57 PM UTC, William wrote: > > > > On Friday, March 18, 2016, Dima Pasechnik <[email protected] <javascript:>> > wrote: > >> >> >> On Friday, March 18, 2016 at 5:33:31 AM UTC, William wrote: >>> >>> >>> >>> On Thursday, March 17, 2016, David Roe <[email protected]> wrote: >>> >>>> Here's a use case where the recent changes to relocatability are really >>>> annoying. I'd like 6 sage installs in an SMC project so that different >>>> groups at Sage Days 71 can work independently. So I tried building a copy >>>> from source and then copying it five times. >>>> >>>> Unfortunately, the relocation script is run at the end of the >>>> installation, making it uncopyable. This is despite the fact that I >>>> refrained from starting Sage after building it. Are there options >>>> available other than building Sage six times? >>>> >>>> I haven't been following the issues involved very closely, but I would >>>> really like to see this feature restored. It's very useful for developing >>>> Sage on servers. >>>> David >>>> >>> >>> Huge +1 >>> >> >> hmm, to what? To have the LD_LIBRARY_PATH back, along with rpath? >> > > Yes definitely. It worked very well for precisely this use case for a > decade. >
well, it was quite often a source of trouble (I can point to dozens of requests for help caused by LD_... paths issues), and then it has reached the point when OSX won't support it. For Sage development proper, it seems to me that it would be a huge hassle to have to design and test both (rpath or no rpath) configurations. Finally, let me point out that the current rpath setup works, and needs just minor tweaks to become as quick as the old one. Thus, again, why would you want it back? (except the "convenience" of it for people who were out of the Sage development loop for a while and missed the moment the switch to rpaths was done). To have an add-on that would allow for a quicker relocation, OK. But an old and broken platform-dependent feature? Please, no, big -1. > >> >>> >>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "sage-devel" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://groups.google.com/group/sage-devel. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> -- >>> Sent from my massive iPhone 6 plus. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Sent from my massive iPhone 6 plus. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
