On 2015-02-19, Michael Orlitzky <mich...@orlitzky.com> wrote: > On 02/19/2015 09:21 AM, Jeroen Demeyer wrote: >> >>> I don't think software was ever delayed for debian. >> If people are against #16997 because it's not compatible with Debian, >> then Debian is *already* slowing down Sage. >> > > It's not incompatibility with Debian that's the problem. Having > dependencies like "whatever was in the git repo at 11:00 on 2015-02-19 > UTC-5" leads to madness. Debian won't do it, because it leads to > madness. So doing things that lead to madness are incompatible with > Debian. The cause and effect are the other way around =)
Yes, but Debian (stable) is often rather hopelessly behind in supporting many things, in particular new hardware and new tools like newer gcc. > > Bundling the git repo is a short-term solution that bones everyone else > (and possibly us, too, if upstream starts reverting commits). A better > solution would be to work with them, settle on a set of commits that are > definitely going to stay, and make a release. Yes, it's more work *right > now*, but most good ideas are. how about making a clone of their git repo and referring to a commit in that clone? This would at least be stable. Basing something on timing rather than on a verifiable repo commit is indeed not good. By the way, that was one of main reasons for me to propose, some time ago, to distribute 3-rd party stuff not as tarballs, but as git submodules. Dima -- 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/d/optout.
