Le 11/07/2012 17:05, Jan Groenewald a écrit :
Hi
On 11 July 2012 16:48, Jeroen Demeyer <jdeme...@cage.ugent.be
<mailto:jdeme...@cage.ugent.be>> wrote:
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!).
Neither Launchpad nor Debian Magic allows one to trivially run "make"
Uh, debian/rules has a target to trigger a build -- and it can
definitely run make. In fact, it generally does just that!
I know that : I learned to package for debian recently. I even have a
few packages I'm trying to push into debian (I need sponsorphip...).
Snark on #debian
--
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
