On 09/15/10 11:01 AM, Nathann Cohen wrote:
If, as Dima mentionned it, I was meant to read this whole conversation
as a "Nathann, could you update the Cliquer SPKG so that your
modifications only appear in a patch folder" (and at some point the
whole of Cliquer's source was in this patch/ folder), this would
indeed require very few work which I can of course take care of. This
could be done now that David is done working on #9871 (which updated
cliquer to p7) and if he does not intend to address #7782 right
now.... Or perhaps should we wait for the p7 version to be included in
a Sage release before updating it again ?
Hmmm... David just created 9870. I will wait until he his done working
on this spkg before touching it again.
Nathann
I did not just create #9870 - it has been open for 8 days. I just CC'ed you it,
as I omitted to do that before. Leif agreed to take ownership of that.
Perhaps you can work with Leif on that. Leif may or may desire your involvement,
though I think you would find working with him rather hard, as even I find his
attention to detail a bit excessive some times. I think you and Leif would clash
even more than you and I!
However, I had already CC'ed you on #9871 and #9833, but you made no comments on
either. Had you read those tickets, you would have been aware of the problems
people were facing with modified upstream code.
There is one technical question you can however answer. Do we need the binary
file "cl" so it can be executed from the command line, or is the library
libcliquer.so sufficient? Perhaps you can state that fact on
http://trac.sagemath.org/sage_trac/ticket/9870
is it will affect how the package gets changed.
Dave
--
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
