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

Make buckygen a standard package #16952

Closed
nvcleemp opened this issue Sep 9, 2014 · 9 comments
Closed

Make buckygen a standard package #16952

nvcleemp opened this issue Sep 9, 2014 · 9 comments

Comments

@nvcleemp
Copy link
Member

nvcleemp commented Sep 9, 2014

Buckygen has been an optional package since May 2013. It has a minimal footprint: just installs one executable that is quite small and compiles quickly. It is the fastest generator for fullerenes and it is GPLv3.

Depends on #16945

Component: packages: standard

Author: Nico Van Cleemput

Branch/Commit: u/nvcleemp/buckygen-standard @ 20a1dd7

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

@nvcleemp nvcleemp added this to the sage-6.4 milestone Sep 9, 2014
@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 9, 2014

Branch pushed to git repo; I updated commit sha1. New commits:

1161342Made buckygen a standard package
20a1dd7Buckygen is no longer an optional package

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 9, 2014

Commit: 20a1dd7

@nvcleemp
Copy link
Member Author

nvcleemp commented Sep 9, 2014

comment:2

I'm not entirely sure these commits are sufficient to make it a standard package, but please enlighten me if there are additional changes needed.

@jdemeyer
Copy link

comment:4

Nico, making a package standard should be discussed on sage-devel. And to be honest, I think your package is much too specialized to be standard.

@vbraun
Copy link
Member

vbraun commented Sep 10, 2014

comment:5

I somewhat agree with Jeroen, the reason for having a set of standard packages is also that other parts of Sage can build on it. Its certainly interesting in its own way, but its not really interconnected with the rest to always compile it. Though we do have a few standard packages that fit that description, too... (e.g. rubiks).

On a legal note, standard packages must be at GPLv3+ compatible (including the or later). Just GPLv3 is not OK. Its fine for optional packages, though.

@jdemeyer
Copy link

comment:6

Replying to @vbraun:

Though we do have a few standard packages that fit that description, too... (e.g. rubiks).

Yes, William once said that package was included for historical reasons. Today it probably wouldn't be added as standard package.

On a legal note, standard packages must be at GPLv3+ compatible (including the or later). Just GPLv3 is not OK. Its fine for optional packages, though.

Really? zn_poly has:

zn_poly: a library for polynomial arithmetic (version 0.9)

Copyright (C) 2007, 2008, David Harvey

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) version 3 of the License.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License,
along with this program (see gpl-2.0.txt and gpl-3.0.txt). If not,
see <http://www.gnu.org/licenses/>.

@vbraun
Copy link
Member

vbraun commented Sep 10, 2014

comment:7

For the zn_poly license see https://groups.google.com/forum/#!msg/sage-devel/-4lMV0n8B3c/3eEWqi4100wJ

@nvcleemp
Copy link
Member Author

comment:8

OK, no problem. The package works fine as an optional package. I just thought that this was the 'natural' evulotion. If specialised packages stay optional, then I'm not going to argue with that.

I wanted to close the ticket, but apparently I can't. I have removed the needs_review status in any case.

@nvcleemp
Copy link
Member Author

comment:9

Replying to @vbraun:

On a legal note, standard packages must be at GPLv3+ compatible (including the or later). Just GPLv3 is not OK. Its fine for optional packages, though.

btw, Buckygen is actually GPLv3+.

@vbraun vbraun removed this from the sage-6.4 milestone Sep 10, 2014
@vbraun vbraun closed this as completed Sep 10, 2014
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