On Thu, Dec 4, 2008 at 10:51 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 4, 10:42 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
>> mabshoff wrote:
>
> <SNIP>
>
>> This worked for me.
>
> Great, that solution works for both of us.
>
> One more thing about installing optional spkgs which depend on other
> optional spkg: From Sage 3.2.1 onward we have the infrastructure to
> query better for installed spkgs, so it is possible to emit better
> error messages about missing installed spkgs without have to hard code
> release numbers. Since the EPD stack probably has some rather deep
> dependencies that might come in useful.
>
This works as follows. Now
sage: install_package('foo')
installs the newest version of foo, or gives an error if it is already
installed.
You can probably use that from the command line in an spkg-install as follows
sage -c "install_package('foo')"
The error behavior is annoying, since you should be able to find out whether
or not the package install succeeded, I guess.
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
