2015-04-24 10:42:12 UTC+2, John Cremona:
Who is the author of hyperellfrob?
OK, I found it (it is actually called hypellfrob): David Harvey.
David, if you are listening -- any comments?
John
I emailed David Harvey and told him about this discussion,
I am forwarding his answer here.
Who is the author of hyperellfrob?
There is a point in addition to Michael's: maintaining a fork which
only differs with respect to libtools packaging is one thing, but we
would also need someone to take responsibility for any bugs found in
the code, if the original author was not able, willing
On 2015-04-24 11:08, Jean-Pierre Flori wrote:
There is even a makefile included
A Makefile is not nearly close to a decent build system.
--
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
On Friday, April 24, 2015 at 10:42:12 AM UTC+2, John Cremona wrote:
On 24 April 2015 at 09:37, John Cremona john.c...@gmail.com javascript:
wrote:
Who is the author of hyperellfrob?
OK, I found it (it is actually called hypellfrob): David Harvey.
David, if you are listening -- any
Whether it is an embedded fork in sage or it gets its own git repo on the
sage github account.. Someone from the sage community would have to fix
bugs in both cases.
Am Freitag, 24. April 2015 10:37:56 UTC+2 schrieb John Cremona:
Who is the author of hyperellfrob?
There is a point in
On 24 April 2015 at 09:37, John Cremona john.crem...@gmail.com wrote:
Who is the author of hyperellfrob?
OK, I found it (it is actually called hypellfrob): David Harvey.
David, if you are listening -- any comments?
John
There is a point in addition to Michael's: maintaining a fork which
On 24 April 2015 at 10:32, than...@debian.org than...@debian.org wrote:
Whether it is an embedded fork in sage or it gets its own git repo on the
sage github account.. Someone from the sage community would have to fix bugs
in both cases.
Yes! But I think that David Harvey *is* a member of the
On Friday, 24 April 2015 14:27:53 UTC+1, John Cremona wrote:
On 24 April 2015 at 10:32, tha...@debian.org javascript:
tha...@debian.org javascript: wrote:
Whether it is an embedded fork in sage or it gets its own git repo on
the
sage github account.. Someone from the sage community
On 2015-04-22 20:17, Michael Orlitzky wrote:
On 04/22/2015 07:57 AM, Jeroen Demeyer wrote:
Hello,
The directory
src/sage/graphs/planarity_c/
is really a copy of an external package
https://code.google.com/p/planarity/
Similarly,
src/sage/graphs/graph_decompositions/rankwidth_c
is really a
On 04/23/2015 04:56 PM, Jeroen Demeyer wrote:
Can't we work with upstream (the authors) to package these?
For starters, none of these seem very active projects. In particular,
hyperellfrob and bernmm have their last release in 2008 and 2009.
Second, what if the authors don't care?
There
On 04/22/2015 07:57 AM, Jeroen Demeyer wrote:
Hello,
The directory
src/sage/graphs/planarity_c/
is really a copy of an external package
https://code.google.com/p/planarity/
Similarly,
src/sage/graphs/graph_decompositions/rankwidth_c
is really a copy of
Hello,
The directory
src/sage/graphs/planarity_c/
is really a copy of an external package
https://code.google.com/p/planarity/
Similarly,
src/sage/graphs/graph_decompositions/rankwidth_c
is really a copy of
http://pholia.tdi.informatik.uni-frankfurt.de/~philipp/software/rw.shtml
What should we
12 matches
Mail list logo
