#17464: Computing the automorphism group of a graph
-------------------------+-------------------------------------------------
Reporter: azi | Owner:
Type: | Status: needs_info
enhancement | Milestone: sage-6.5
Priority: major | Resolution:
Component: graph | Merged in:
theory | Reviewers:
Keywords: | Work issues:
Authors: | Commit:
Report Upstream: N/A | f8dcb7e4ffca76715b478ada498be1714e0f38f1
Branch: | Stopgaps:
u/azi/bliss |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by ncohen):
Yoooooooooooo !
Well, so far your branch does not look "that bad". The only weird thing is
that I do not get why this bliss branch should do that modifications `:-P`
{{{
#!diff
+ :meth:`~GenericGraph.geodetic_number` | Returns the geodetic number
of the given graph.
}}}
The right way to write this code, however, begins as you say by writing
the spkg, as nobody can test it without it. And the right way to do that,
as usual is copy and paste.
1) There is a developer's manual that I am trying to improve these days.
There is a section I never read about exactly that:
http://www.sagemath.org/doc/developer/packaging.html. If you find anything
wrong/unclear in there, please fix it if you can. We must make this clear
to everybody. If you do not understand, tell me where it is and I will try
to fix it.
2) spkgs are rather simple nowadays. The code that **installs** the
program is a Sage code, like any other. You will find it in
SAGE_ROOT/build/. Take a look at the structure of `buckygen`, for
instance: it is an optional graph package, just like bliss will be.
3) That was for the Sage code, but the non-sage code (i.e. the source code
of bliss) must be stored in the SAGE_ROOT/upstream folder. You will figure
out that the code in build/ is actually instruction about what to do with
the bliss-version.tar.bz2 that must be there, and which is only the
official bliss release.
4) Then there are he "checksums":
http://www.sagemath.org/doc/developer/packaging.html#checksums
So before continuing with this you should create a ticket to add bliss as
a spkg. It could be quick, and if you have time right now we can settle it
fast, I won't get to bed before one hour at least, I can review it before.
A ticket that adds a new package should contain:
1) A branch that adds the required files in the build/ folder
2) A .tar.bz2 file (hosted wherever you like) that I should download in
the upstream/ folder before typing "sage -i bliss".
I am a bit offline this evening because I have a very short ethernet cable
next to an uncomfortable chair. I come back from time to time to check my
emails `:-P`
Good luck !
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/17464#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
