Le 11/07/2012 16:48, Jeroen Demeyer a écrit :
On 2012-07-11 16:02, Julien Puydt wrote:
Well, apparently some longer explanations are needed.
I understand all of this, but that wasn't my question.
Let me try to phrase my question better:
Currently, Jan Groenewald has a Debian Sage source package which is in
reality a Sage binary with some Debian magic added to it. That Debian
magic allows Launchpad to extract the binary and repackage it such that
end-users can install it.
Now, why cannot Jan Groenewald replace the Sage binary in his source
package by a Sage source in the source package and then trivially adjust
the Debian magic to simply run "make" on Launchpad (not in the end-user
install!).
Oh ; it would be technically possible, but I'm actually surprised the
server admins haven't already protested against such a big binary blob.
They definitely wouldn't like a source package which hides a hundred of
others -- especially when those others are already in ubuntu separately!
I have better hopes for the debian work going on : separate packages for
separate spkg. No sage-as-a-distribution, but a serious
sage-as-a-software packaging.
It's not there yet, but things are getting in place.
Snark on #sagemath
--
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
