On 04/22/2013 11:14 AM, Jeroen Demeyer wrote:
On 04/22/2013 09:57 AM, Felix Salfelder wrote:
do you see disadvantages in treating sage parts as modules?
It doesn't even make sense to treat them as modules, since they are not
independent. libcsage means nothing without the Sage Python library, the
Sage Python library requires libcsage and the scripts make no sense
without Sage.
It seems to me these three things belong into a Debian source package
together and Sage should provide configure, build and install targets
for them together (don't know if real configure script/makefile or a
script invoking multiple other builds). The Debian source package would
split the resulting files into binary packages python-sage, libsagec
etc. which is a standard thing we do for most large projects we package
in Debian.
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
