Le lundi 24 octobre 2016 16:14:29 UTC+2, Dima Pasechnik a écrit :
>
> +1
>
> IMHO we don't really have to vote on it, as this is basically splitting of 
> a standard package into several,
> as enforced by upstream.
>

Indeed. However, the suggestion made on the similar stream on curl (i. e. 
install only if not installed systemwide) is interesting. It taxes my 
(admittedly limited) knowledge of the Unix configure tools (and autotools), 
but it's worth a try.

However, what happens when a library exists at Sage's build time and is 
later pulled off the system ?

Bonus question : can an spkg-install script recursively call 
$SAGE_ROOT/sage -i <some other package> and get the return status back ?

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to