Le 07/08/2017 à 11:54, Erik Bray a écrit :

> I'm working on a better solution to this as part of a more general
> reworking of how Sage's dist handles dependencies that can be
> fulfilled by multiple packages (in this case the dependency being
> 'python'--specifically the Python used for Sage itself).  I have a
> prototype at [1] but there are several things about it I'm unhappy
> with, and I want to redo it on top of some even lower-level overhauls
> I'm working on (e.g. [2]).

I would like to make the point that having a packaging which is :
- versioned ;
- with dependency resolution ;
- including virtual packages ;
is definitely a sage-as-a-distribution problem.

Please take into account that sage-as-a-software should be kept easily
package-able by other distributions.

Snark on #sagemath

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