kaimmello wrote: >> I think Martin is not suggesting to use the official Debian packages but >> to provide our own repository, >> which means we would (eventually) maintain our own deb versions of GAP, >> Maxima, etc. This >> is a great long term goal, IMHO. >> > > IMHO it's quite dangerous to provide and maintain our own packages of > all components (GAP, Maxima, etc) because > > - it requires much work that, if lacking, may cause SAGE package to > become obsolete > - if, on the contrary, all efforts are concentrated on SAGE, the > traditional packages of GAP, Maxima, etc, may become obsolete, and it's > not a good idea to grow by cutting our own roots. > - if SAGE team works on one component but then the team of that > component comes out with a major release not including SAGE patches, we > can occur in a fork, and is it's IMHO very bad. > - by having more than one version of the same component, for example > one stand-alone and one included in SAGE, we risk to betray the spirit > of the free software, i.e. to use the available pieces of software. > Doesn't it recall the "Hell of DLL's" in Windows world?? SAGE has been > up to now the best "glue" for the scientific software...IMHO it would > be really nice to glue also all existing debian packages.
I'm agree with the 90% of your comments, but the last one will be strange. The main problems is related with debian policy's that gave packages a better quality with QA phase, etc .. and this give them with some older packages. I think that we could no work this some debian packages directly, we have to look for some solution that help SAGE keep the correct software. As i could remember the biggest problem could be related with python and pyrex, sage versions are patched with non-official solutions that never will be with debian ... > My hope would be to collaborate with the maintainers of the existing > packages in order to update them with SAGE requirements in mind. I think this is a good idea, but could be very difficult because there are debian guidelines that every package must agree. As i say'd the normal time to package something like SAGE is about two year to be agree with debian standards. But how about other platforms, i think that could be interesting to form a sage packaging team that could do it for some platforms,isn'it? Pere > Best regards. > > Tiziano > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
