Dear All, I have a philosophical question concerning how we implement things in sage. More precisely I am concerned on how we deal with external packages.
Right now we implement our own package management system and we install (almost) all our dependencies under whichever prefix the user gives to sage. On the plus side we now have complete control on which version of each package we are dealing with, we have the ability to patch each of them diverging from their upstream version if we need to and our users only need a single command to install the whole circus. On the minus side though, there is a lot of duplicated stuff around. For example on my machine I have 28 packages that are installed both as part of my system and as part of sage and 99 packages unique to sage. This looks to me like a complete waste of resources (especially when you consider that among the duplicated things there are some heavy package to compile like gcc). I can see few more drawbacks to this approach. For example we have to maintain the packages we ship with and it makes harder to use sage as a library rather than a CAS. Is there any plan to remove this issue in the future? If so, who do I talk to in order to contribute? Best S. -- 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.
