Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up Cliquer's spkg-install #9870

Closed
sagetrac-drkirkby mannequin opened this issue Sep 7, 2010 · 22 comments
Closed

Clean up Cliquer's spkg-install #9870

sagetrac-drkirkby mannequin opened this issue Sep 7, 2010 · 22 comments

Comments

@sagetrac-drkirkby
Copy link
Mannequin

sagetrac-drkirkby mannequin commented Sep 7, 2010

The spkg-install file for Cliquer could do with a lot of cleaning up. Some examples of the problems are:

  • There are flags set for the C++ and Fortran compilers, though the code is only C.
  • There's code to check for a mix of Sun and GNU compilers, which is pointless since there is only 1 compiler used.
  • Lots of unnecessary environment variables are set.
  • Use make instead of $MAKE.
  • Runs tests in spkg-install instead of spkg-check.

None of these issues are currently causing any problems, but should be resolved at some point

Depends on #14349

CC: @nathanncohen @sagetrac-mvngu

Component: packages: standard

Author: Jeroen Demeyer

Branch: 2ffeeb7

Reviewer: Jean-Pierre Flori

Issue created by migration from https://trac.sagemath.org/ticket/9870

@sagetrac-drkirkby sagetrac-drkirkby mannequin added this to the sage-5.11 milestone Sep 7, 2010
@nexttime
Copy link
Mannequin

nexttime mannequin commented Sep 9, 2010

comment:1

To tranquilize Dave :-)

I've made several comments at tickets related to Cliquer, e.g. #9833 and #9871.

I think this should then be a follow-up of #9871, despite the numbers.

@nexttime nexttime mannequin assigned nexttime and unassigned sagetrac-GeorgSWeber Sep 9, 2010
@nathanncohen
Copy link
Mannequin

nathanncohen mannequin commented Sep 15, 2010

comment:3

Hello !

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?

No, the cl file is not used, and this is precisely what the Sage code included in cliquer is useful for : directly calling the library's functions with a Graph object using the Graph structure it expects to find, without having to create an ugly temporary file to call the executable on it :-)

Nathann

@sagetrac-drkirkby
Copy link
Mannequin Author

sagetrac-drkirkby mannequin commented Nov 7, 2010

comment:5

Leif, you were keen to take ownership of this. Has anything happened with it?

Dave

@sagetrac-drkirkby
Copy link
Mannequin Author

sagetrac-drkirkby mannequin commented Mar 23, 2011

comment:6

I ask once again. Any chance of you sorting this out Leif, since you wanted to take ownership of it.

Dave

@jdemeyer
Copy link

comment:7

See #11227 for another issue with cliquer, unrelated to this ticket.

@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@jdemeyer
Copy link

Author: Jeroen Demeyer

@jdemeyer
Copy link

comment:9

I'll tackle this.

@jdemeyer

This comment has been minimized.

@jdemeyer jdemeyer changed the title Clean up Cliquer's Makefile and spkg-install Clean up Cliquer's spkg-install Jan 16, 2014
@jdemeyer
Copy link

Branch: u/jdemeyer/ticket/9870

@jdemeyer
Copy link

Commit: 5f55f5b

@jdemeyer
Copy link

New commits:

f55a304python-sage work without cliquer patching (#14349)
aecdf29module_list: add cl.c to cliquer.so sources (#14349)
25edb2ftrac #14349: rebase on 6.1.beta4
6253068trac #14349: move cl.* to cliquer/
9f04e98Merge remote-tracking branch 'origin/develop' into HEAD
5f55f5bClean up cliquer package

@jdemeyer
Copy link

Dependencies: #14349

@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@jpflori
Copy link

jpflori commented Feb 20, 2014

Changed commit from 5f55f5b to 2ffeeb7

@jpflori
Copy link

jpflori commented Feb 20, 2014

Reviewer: Jean-Pierre Flori

@jpflori
Copy link

jpflori commented Feb 20, 2014

comment:14

Don't know why trac was not able to merge the branch as I encountered no conflicts when merging it.

I've made a few changes to make the script more like the "new" scripts as described in the dev guide, you may not be happy with them and are very welcome to change them back.
Otherwise let's positively review this ticket.

Anyway, I'm going to autotoolify cliquer, post it in a follow-up ticket and suggest it upstream.
The Makefile is just too awful right now.


New commits:

92dd8c8Merge remote-tracking branch 'trac/develop' into ticket/9870
2ffeeb7Slight changes to cliquer install script.

@jpflori
Copy link

jpflori commented Feb 20, 2014

Changed branch from u/jdemeyer/ticket/9870 to u/jpflori/ticket/9870

@jpflori
Copy link

jpflori commented Feb 20, 2014

comment:15

I've sent an email upstream about the possibility of releasing an official version including some of the Debian's patches (http://anonscm.debian.org/gitweb/?p=debian-science/packages/cliquer.git;a=tree;f=debian/patches;hb=HEAD) and an autotoolified build system.

@jdemeyer
Copy link

comment:16

I think set -e is a good thing and should be used more. So I reverted that change.

@jdemeyer
Copy link

Changed branch from u/jpflori/ticket/9870 to u/jdemeyer/ticket/9870

@vbraun
Copy link
Member

vbraun commented Feb 22, 2014

Changed branch from u/jdemeyer/ticket/9870 to 2ffeeb7

@jpflori
Copy link

jpflori commented Feb 24, 2014

Changed commit from 2ffeeb7 to none

@jpflori
Copy link

jpflori commented Feb 24, 2014

comment:19

FYI, upstream has nicely answered my questions.
They don't really mind cliquer being distributed in different forms in various places and don't plan on releasing any new upstream version "in the next ten years or so (or ever?)".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants