I'd like to write an optional sage package B that depends on another 
optional sage package A.

What is the standard way to achieve that

   sage -i B

looks at http://www.sagemath.org/packages/optional/ for B and first 
installs A if A is not yet locally installed?

Is there already any automatic dependency tracking in sage's package 
installation scripts?

To be more precise. In my case I need that the installation of B does 
something like 'sage -i -s A', i.e. keeps the build dir of A.

Any hint is appreciated.

Ralf

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to