Re: [sage-devel] Re: Location of ecl packages

2019-02-01 Thread mmarco
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 "") > > On Fri, Feb 1, 2019 at 8:

[sage-devel] Second opinion for first-time-reviewed ticket?

2019-02-01 Thread Friedrich Wiemer
One of my ticktes was reviewed by Lukas Stennes, who's first Sage review this is: https://trac.sagemath.org/ticket/26009 Does anyone wants to have an additional look over his review and my patch? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: Location of ecl packages

2019-02-01 Thread Dima Pasechnik
did you try what's described in https://www.quicklisp.org/beta/faq.html : (quicklisp-quickstart:install :path "") On Fri, Feb 1, 2019 at 8:32 PM mmarco 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

Re: [sage-devel] Re: Location of ecl packages

2019-02-01 Thread mmarco
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 unde

Re: [sage-devel] Re: Location of ecl packages

2019-02-01 Thread Dima Pasechnik
On Fri, Feb 1, 2019 at 4:23 PM mmarco 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 > director

[sage-devel] Re: Location of ecl packages

2019-02-01 Thread mmarco
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 woul

Re: [sage-devel] sage crash report

2019-02-01 Thread Aranka Hrušková
Thank you both Vincent and Thierry! I have deleted the repository (no files were saved there -- I have a completely fresh install of Ubuntu 16 and there are virtually no files anywhere), and sage seems to be working now! pá 1. 2. 2019 v 14:24 odesílatel Thierry napsal: > On Fri, Feb 01, 2019 at

Re: [sage-devel] sage crash report

2019-02-01 Thread Thierry
On Fri, Feb 01, 2019 at 01:59:06PM +0100, Vincent Delecroix wrote: > Hi > > What you did seem correct. However the following > > > $ ls -ld/home/a/.sage > > drwx-- 7 root root 4096 jan 26 19:54/home/a/.sage > > is very wrong. The root (the super user on your computer) owns > the repository

Re: [sage-devel] sage crash report

2019-02-01 Thread Vincent Delecroix
Hi What you did seem correct. However the following $ ls -ld/home/a/.sage drwx-- 7 root root 4096 jan 26 19:54/home/a/.sage is very wrong. The root (the super user on your computer) owns the repository /home/a/.sage. But it should just be the user "a". Just delete this repository via

Re: [sage-devel] sage crash report

2019-02-01 Thread Aranka Hrušková
Dear Vincent, The output of $ ls -ld /home/a/.sage is drwx-- 7 root root 4096 jan 26 19:54 /home/a/.sage During the installation process I was following the steps described on the sage website . If I remember correctly, I down