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
Comments
Commit: |
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. |
comment:4
Nico, making a package standard should be discussed on |
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. |
comment:6
Replying to @vbraun:
Yes, William once said that package was included for historical reasons. Today it probably wouldn't be added as standard package.
Really?
|
comment:7
For the |
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. |
comment:9
Replying to @vbraun:
btw, Buckygen is actually GPLv3+. |
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
The text was updated successfully, but these errors were encountered: