On 18 December 2013 16:54, Robert Bradshaw wrote:
> You should still be able to do ./sage -i /path/to/xxx.spkg
... but only if the spkg-install has been updated, which my local copy
hasn't, so I get errors (SAGE_DATA not defined).
>
> You're right, the online one should have worked too. Someone
You should still be able to do ./sage -i /path/to/xxx.spkg
You're right, the online one should have worked too. Someone updated
the spkg without updating the checksums (maliciously or otherwise).
On Wed, Dec 18, 2013 at 8:48 AM, John Cremona wrote:
> I have the habit of installing a short list o
I have the habit of installing a short list of optional spkgs whenever
I build a new Sage version on my machine, and to avoid downloads I
have been keeping the .spkg files locally, and using sage -i
/xxx.spkg
I realise that this will probably not work (or will it?) with the the
git arrangement, e.
