the short answer: quicklisp is not for this:

12:02 -!- Irssi: #lisp: Total of 302 nicks [1 ops, 0 halfops, 0
voices, 301 normal]
12:02 -!- Channel #lisp created Sun Aug  3 22:30:32 2003
12:02 -!- Irssi: Join to #lisp was synced in 0 secs
12:03 < dimpase_> how does one install quicklisp into a custom
location, rather than ~/quicklisp ?
12:05 < dimpase_> their FAQ is rather unclear on it, and in my setup
(require :ecl-quicklisp) starts installing things into
                  ~/quicklisp straight away.
12:06 -!- akoana [~a...@ge10-rb1100.vie.funkinternet.at] has joined #lisp
12:07 < Inline> i suppose there are 2 ways
12:08 < Inline> maintain a symlink to your quicklisp (wherever it is)
12:08 < Inline> i.e. let ~/quicklisp be a symlink
12:08 < Inline> or set an ENV variable
12:10 < phoe> dimpase_: you are free to move ~/quicklisp/ anywhere
after it's installed
12:10 < phoe> then load the setup.lisp file from the new location
12:10 < dimpase_> the scenario we talk about is to use quicklisp to
install a package systemwide.
12:11 < dimpase_> one does not want 100 students creating ~/quicklisp
and downloading stuff there...
12:13 < dimpase_> seems to be a reasonable thing to do - perhaps I
miss something trvial here...
12:13 < phoe> you don't want to use Quicklisp in that case
12:13 < phoe> quicklisp operates with the assumption that users can
download arbitrary stuff into the Quicklisp directory
12:14 < phoe> basically, your Lisp implementation will have RW access
to the quicklisp homedir

On Sat, Feb 2, 2019 at 1:02 AM mmarco <mma...@unizar.es> wrote:
>
> I tried that, it complains about quicklisp being already configured
>
> El viernes, 1 de febrero de 2019, 23:36:34 (UTC+1), Dima Pasechnik escribió:
>>
>> did you try what's described in https://www.quicklisp.org/beta/faq.html :
>>
>> (quicklisp-quickstart:install :path "<your path here>")
>>
>> On Fri, Feb 1, 2019 at 8:32 PM mmarco <mma...@unizar.es> wrote:
>> >
>> > 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> 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+...@googlegroups.com.
>> > To post to this group, send email to sage-...@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/sage-devel.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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.

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