On Sun, Jan 12, 2014 at 9:15 PM, Volker Braun <vbraun.n...@gmail.com> wrote:
> At the risk of veering even further off-topic, I would like to give up "tree
> relocation" as it is currently defined. Its cumbersome (need to check that
> we haven't been moved all the time) and insecure.
>
> For relocatable binaries, we build with / rewrite rpaths to be relative and
> make all libtool .la files have relative paths. This may require further
> dependencies, like tools to rewrite rpaths. Also, once you unpack the binary
> and start compiling further stuff in its directory it may or may not be
> relocatable any more. But really the goal is to distribute binaries, not
> allow you to move your sage directory around all the time. All modern
> linuxes and intel OSX allow relative rpaths and its modification with the
> help of special tools.

I don't think this is off topic and I think you make a very good
point.  Relocation (as I defined it) is not the goal.  The goal is to
build user-installable binaries.  If what you suggest above works with
a given build system, then that satisfies the design constraints.

Has anybody listed the functionality constraints, i.e., the problem we
are discussing?  Here is a very rough first stab.

   - user-installable binaries
   - tested (as Volker defined above)
   - supports our platforms, e.g., OS X, Solaris, Linux, Cygwin, ??
   - parallel build from source must be fast
   - upgrades of binaries without having to compile anything would be
nice (we do not have that now)
   - ability to uninstall packages (which we do not have now)

I think building in parallel is the part of the current build system
that was by far the hardest, and for which most effort has probably
been spent.   The time it takes to do a full build from source on a
fast  multi-core machine is an absolutely critical benchmark for
whatever is proposed.

 -- William

>
>
>
> On Monday, January 13, 2014 12:00:55 AM UTC-5, William wrote:
>>
>> Of course, relocation is really a way to solve the problem "build a
>> sage binary once and make it available to other people to install in
>> their home directory".   I don't know of any other way to solve that
>> problem.   I also don't know if *any* of the non-Sage build systems in
>> this thread support relocation of binaries.
>>
> --
> 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 sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/groups/opt_out.



-- 
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to