Le 16/01/2013 11:24, Volker Braun a écrit :
On Wednesday, January 16, 2013 9:49:22 AM UTC, Timo Kluck wrote:
And then it would be nice if we'd distribute two tarballs for
downstream to package, the one depending on the other: sage (or
sagemath) which is the command line interface and the notebook, and
something like python-sage (in the Debian naming convention) which
is just the python library.
Basically you are saying we should try to mimic the debian packaging
system. That doesn't make sense to me, the Sage tarball should be all of
the code in Sage and the distribution can split it up any way they want.
Thats how 99% of projects out there work.
I disagree : projects out there ship their code. And their code says "I
depend on ...".
They don't ship their code and the code of all their deps and the code
of all their deps and the code of all their deps, etc.
Sage ships patch, bzip2, gcc, python and mercurial, to name a few.
Snark on #sagemath
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.