Yes, but what I mean is that when you do that, kenzo code is compiled into 
the user's home directory (look under ~/quicklisp). So if there are several 
users in the same machine, it will be compiled for each user the first time 
they use kenzo. It would make more sense to install it somewhere under 
$SAGE_LOCAL when the package is installed, and then it would be available 
immediately for every user.

That is my question: how can we force quicklisp  to install it (ans later 
look for it) under $SAGE_LOCAL instead of ~/quicklisp

El viernes, 1 de febrero de 2019, 18:06:59 (UTC+1), Dima Pasechnik escribió:
>
> On Fri, Feb 1, 2019 at 4:23 PM mmarco <mma...@unizar.es <javascript:>> 
> wrote: 
> > 
> > Thanks for the answers. 
> > 
> > I just realized that the package I want to install is available by 
> quicklisp, so maybe it would be easyer to install it using that. 
> > 
> > However I noticed that quicklisp installs evetything in the users home 
> directory, even if it is called from the sage environment. That would be ok 
> for single user systems, but might be a problem if we have a system wide 
> sage install for multiple users. 
> > 
> > Do you know if there is a way to configure quicklisp inside sage to use 
> the sage directory for its instalataions? 
>
> it just works, in a way: 
>
>
>  $ ./sage --ecl 
> ECL (Embeddable Common-Lisp) 16.1.2 (git:UNKNOWN) 
> [...] 
> > (require :ecl-quicklisp) 
>
> ;;; Loading #P"/mnt/opt/Sage/sage-dev/local/lib/ecl/ecl-quicklisp.fas" 
> [...] 
> > (ql:quickload "kenzo") 
> [...] 
> ("kenzo") 
> > (ql:quickload :kenzo-test) 
> [...] 
>
> (fiveam:run! :kenzo) 
>
> Running test suite KENZO 
> ... 
>

-- 
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