>> mean that a sage installation should never install anything that is >> already available in a standard distribution.
> Even if that means that the Sage testsuite fails because distribution > packages have a bug that isn't fixed upstream yet? Thats an important > policy question and we never had that discussion.... Come on, it's clear that a decent system that wants to build on existing software has to specify the least requirement for that existing software. If the underlying distribution does not fulfil that requirement, something else has to be done. My initial question was "What requirement for git does Sage have?" Where can I find a list of version number for all the packages that are available in some distribution and *could* be used by Sage. In other words why did my sage build want to install git on Debian 7 although I already have it installed. Does that mean the git that comes with Debian 7 has a bug that sage cannot live with? I guess not. > can you summarize what the problems > Build it on all supported platforms and then report back. This ought to be > the most important output of the project but I never saw it. I don't have the feeling that this answers my question. :-( Ralf -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
