Op maandag 22 april 2013 09:57:19 UTC+2 schreef Felix Salfelder het volgende: > > do you see disadvantages in treating sage parts as modules? > > maybe it doesnt matter much, whether c_lib and scripts are in the same > module or not, for distribution purposes it makes sense to have > python-sage and sagenb seperated. for gentoo it makes sense to have > c_lib seperated. most importantly: /keep/ things seperated, so > distributions can pick it up (and can pick it up tomorrow, after someone > has reinvented sage "the distribution"). > > I haven't followed this thread entirely, but I thought I should mention something that Julian Rüth and I are working on. It is related to separating Sage's binary files into different binary packages, which seems to be what you're discussing.
We're trying to replace the current spkg system (actually the spkg system like it exists in the git repo) by some version of Gentoo's portage. This would be similar to the lmonade project, except that it's trying to be a smooth transition from the current source distribution. As soon as this works, then it would be possible to use this to generate debian packages, since portage keeps track of installed binary files for packages. So the debian/rules file could query portage for which files should go into which binary package. The only technical obtacle I can think of is that you'll likely want to eventually install the sage tree somewhere under /usr/lib/sage, or /opt/sage or something. So portage should compile for that prefix. But it should "install" under debian/tmp. That should be possible, especially since portage uses its own DESTDIR too. Best, Timo -- 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.
