|
From: Carsten S. <c.s...@t-...> - 2017-11-16 15:04:14
|
Hi, I mainly work on packaging the KiCad EDA tool [1] for Debian. The next version 5 of KiCad has implemented Spice simulation based on libngspice. Unfortunately due some license issues the ngspice package is not part of the official Debian part and only available in the non-free repositories [2]. So right now I can't rely and depend on ngspice for KiCad. If I want to do that I need to make ngspice fit for the Debian main archive. In the past there was some started effort to solve the licensing issue on the ngspice source that was also forwarded to the debian-legal mailing list [3]. Now a new version ngspice-27 was released and so far I could read and understand the file COPYING in the top root folder of the source some re-licensing was done. Yeah! Unfortunately this is not really helpful for me, as we need to be sure the source we try to bring into Debian main is compatible with the Debian Fee Software Guide (DFSG) [4], the ftpmasters and other Debian Developers taking the DFSG really serious (that's fully correct!) and files or folder with no clear license can't be introduced into the main archive. So for me it would really useful if Upstream could help me to figure out what file is licensed by which license. The file COPYING contains the following part: > The following table is a summary of license status: > Author License Notes > > numparam Georg Post LGPL Applies to the code in > frontend/numparam > adms Laurent Lemaitre LGPL Applies to scripts in the > spicelib/dev/adms > tclspice Stefan Jones LGPL TCL integration > cider U. of California New BSD Device level simulator > xspice Georgia Tech. Public D Mixed signals > spice U. of California New BSD Analog circuit simulation > table.cm Holger Vogt GPL Code model shared library > containing GPLed code. For me as one person which is not familiar the details of the ngspice source it's not clear what this list is meaning. What is the respective addressed source in this list? A lot of the folders inside the source doesn't contain any extra licensing information and it's really hard to collect the various licensing information. :-/ The folder ./doc can't distributed in Debian at all due the used SPICEDOC license (according to doc/ngspice.texi). Would it be possible if the devs could help me to write down the used licenses for the various parts of ngspice? So far I got the following assumption about used licenses. ./contrib, mix of LGPL-2, GPL-2, GPL-2+, BSD-3-clause ./doc, SPICEDOC (not DFSG clean) ./examples, which license? new BSD? ./man, probably new BSD? .src, probably all files new BSD ├── ciderlib ├── frontend, parts use GPL-2 ├── include ├── maths ├── misc ├── spicelib, contains some non-free licensed files e.g NXP ├── unsupported └── xspice ./tests, probably all files new BSD ./visualc, doesn't interesting for Debian ./xgraph, BSD-3-clause If the license question could be made clear it would also help other users of ngspice. Thanks! [1] https://tracker.debian.org/pkg/kicad [2] https://packages.debian.org/source/unstable/ngspice [3] https://lists.debian.org/debian-legal/2016/10/msg00022.html [4] https://wiki.debian.org/DFSGLicenses -- Regards Carsten Schoenert |
|
From: Holger V. <hol...@un...> - 2017-11-24 22:08:38
|
ngspice licenses All ngspice files are covered by the 'New BSD' (3-clause BSD) except for: ngspice/doc SPICEDOC, not compatible to DFSG considered outdated ngspice/contrib various, considered outdated ngspice/m4 ?, compatible to New BSD ngspice/src/tclspice.c LGPLv2 all files in ngspice\src\maths\sparse MIT_SPARSE, compatible to New BSD ngspice/src/spicelib/devices/adms/ekv ngspice/src/spicelib/devices/adms/hicum0 ngspice/src/spicelib/devices/adms/hicum2 ngspice/src/spicelib/devices/adms/psp102 copyright info, but no license information given ngspice/src/spicelib/devices/adms/mextram Educational Community License version 1.0 ngspice\src\spicelib\devices\adms\admst LGPLv2.1 ngspice\src\spicelib\devices\ndev public domain ngspice\src\xspice public domain except for ngspice\src\xspice\icm\table\ GPLv2 or newer ngspice\src\frontend\numparam LGPLv2 or newer ngspice\src\ciderlib UCB agreed to put this under New BSD, but still under discussion ngspice manual (https://sourceforge.net/p/ngspice/ngspice-manuals/ci/master/tree/) Creative Commons Attribution Share-Alike (CC-BY-SA) v4.0 (still to be included in an update to ngspice-27 release) My personal recommendation on what to do to obtaim a DFSG compatible build would be: Skip the following: all files in ngspice/doc all files in ngspice/contrib all files in ngspice\src\spicelib\devices\adms\ all files in ngspice\src\ciderlib Add the copyright notice to the actual ngspice manual (will be done immediately). So adms and CIDER would not be available. For KiCAD users this would be of absolutely no concern. |
|
From: Holger V. <hol...@un...> - 2017-11-24 23:32:39
|
I have made a short check using CYGWIN 64 bit:
remove ngspice/spicelib/devices/adms.
remove all the contents of ngspice/ciderlib, so keep just the empty folder.
edit ngspice/configure.ac
@@ -1145,15 +1145,10 @@ AC_CONFIG_FILES([Makefile
src/spicelib/devices/nbjt2/Makefile
src/spicelib/devices/numd/Makefile
src/spicelib/devices/numd2/Makefile
src/spicelib/devices/numos/Makefile
src/spicelib/parser/Makefile
- src/ciderlib/Makefile
- src/ciderlib/input/Makefile
- src/ciderlib/support/Makefile
- src/ciderlib/oned/Makefile
- src/ciderlib/twod/Makefile
src/frontend/Makefile
src/frontend/numparam/Makefile
src/frontend/help/Makefile
src/frontend/parser/Makefile
src/frontend/plotting/Makefile
Then use
../configure --with-ngshared --disable-debug --enable-xspice
--enable-pss --enable-relpath --enable-openmp CFLAGS="-O2" LDFLAGS="-s"
make
make install
in the CYGWIN64 bash shell to compile ngspice.so.
|
|
From: Holger V. <hol...@un...> - 2017-11-25 09:04:48
|
An update to the license list: ngspice licenses All ngspice files are covered by the 'New BSD' (3-clause BSD) except for: ngspice/doc SPICEDOC, not compatible to DFSG considered outdated ngspice/contrib various, considered outdated ngspice/m4 ?, compatible to New BSD ngspice/src/tclspice.c LGPLv2 all files in ngspice\src\maths\sparse unnamed MIT license, compatible to New BSD ngspice/src/spicelib/devices/adms/ekv ngspice/src/spicelib/devices/adms/hicum0 ngspice/src/spicelib/devices/adms/hicum2 ngspice/src/spicelib/devices/adms/psp102 copyright info, but no license information given ngspice/src/spicelib/devices/adms/mextram Educational Community License version 1.0 ngspice\src\spicelib\devices\adms\admst LGPLv2.1 ngspice\src\spicelib\devices\ndev public domain ngspice\src\spicelib\devices\hisim2 ngspice\src\spicelib\devices\hisimhv1 ngspice\src\spicelib\devices\hisimhv2 unnamed Hiroshima University and STARC license, compatible to New BSD ngspice\src\xspice public domain except for ngspice\src\xspice\icm\table\ GPLv2 or newer ngspice\src\frontend\numparam LGPLv2 or newer ngspice\src\ciderlib UCB agreed to put this under New BSD, but still under discussion ngspice manual (https://sourceforge.net/p/ngspice/ngspice-manuals/ci/master/tree/) Creative Commons Attribution Share-Alike (CC-BY-SA) v4.0 (still to be included in an update to ngspice-27 release) My personal recommendation on what to do to obtaim a DFSG compatible build would be: Skip the following: all files in ngspice/doc all files in ngspice/contrib all files in ngspice\src\spicelib\devices\adms\ all files in ngspice\src\ciderlib Add the copyright notice to the actual ngspice manual (will be done immediately). Check if Hiroshima University and STARC licenses are compatible to DFSG So finally adms and CIDER would not be available. For KiCAD users this would be of absolutely no concern. |
|
From: Holger V. <hol...@un...> - 2017-11-25 10:10:15
|
The update to the manual is done and available at https://sourceforge.net/p/ngspice/ngspice-manuals/ci/master/tree/. However, to be compliant with DFSG, considering the ongoing discussion, chapter 30 has to be emptied (removing the CIDER description), if a short term solution is required. Holger |
|
From: Carsten S. <c.s...@t-...> - 2017-11-25 08:28:08
|
Hello Holger, thank you very much for your detailed answer and your quick testing! That helps a lot. Am 24.11.2017 um 23:08 schrieb Holger Vogt: > ngspice licenses > > All ngspice files are covered by the 'New BSD' (3-clause BSD) except for: ... > ngspice manual > (https://sourceforge.net/p/ngspice/ngspice-manuals/ci/master/tree/) > Creative Commons Attribution Share-Alike (CC-BY-SA) v4.0 > (still to be included in an update to ngspice-27 release) I have dropped that folder/source for now, it's easily to re-add that later if the license statement is really clear for people from outside visible. To tear down some workload for now I take a look at this later. >From a Debian POV this is a extra source tarball that needs some more things to do. CC-BY-SA 4.0 is fine from a Debian DFSG view. > My personal recommendation on what to do to obtain a DFSG compatible > build would be: > > Skip the following: > all files in ngspice/doc > all files in ngspice/contrib > all files in ngspice\src\spicelib\devices\adms\ > all files in ngspice\src\ciderlib > > Add the copyright notice to the actual ngspice manual (will be done > immediately). I can't add anything about the copyright or license to that folder or content that isn't there. I could add a note in the debian/copyright file as a quote from a email from that mailing list that has some kind of official note by the developers or project and copyright holders in between times. OTOH I would start a upload to the experimental path of Debian at all to catch issues and problems in the packaging without regressions for users of unstable or testing. That gives the possibility to update the package nevertheless we can add the manual at all later. The README for the Debian package needs some explanation what's the difference to the upstream source. I'm aware of that and have some things about that all in my mind. For sure I will ask further questions here on the list. > So adms and CIDER would not be available. For KiCAD users this would be > of absolutely no concern. Yes, absolutely. KiCad only needs libngspice0. If some files of simulation for specific devices are not included in the Debian packages is no problem if this is all explained to the users in the README file in /u/s/d/ngspice e.g. Thanks again for your answer, I can now do more work to get ngspice-27 into Debian main. Maybe the developers of ngspice can add a file LICENSES.txt on the top of the source to make it easier to find the various license relationship or expand that part in README.txt? Even better would be a snippet about copyright and license in each file. There are some parser out there that can do the boring and time consuming job of collecting the information. But this need some used standard here. https://reuse.software/practices/ -- Regards Carsten Schoenert |
|
From: Holger V. <hol...@un...> - 2017-11-25 11:00:00
|
Carsten, please consider adding the XSPICE extensions to your KiCad distribution. This is not for the digital part, which may become of interest later, but for the Polynomial Source Compatibility. Many standard vendor OpAmp models are using polynomal sources that ngspice is offering only via XSPICE. Holger > Yes, absolutely. KiCad only needs libngspice0. If some files of > simulation for specific devices are not included in the Debian packages > is no problem if this is all explained to the users in the README file > in /u/s/d/ngspice e.g. > |
|
From: Holger V. <hol...@un...> - 2018-03-17 10:29:10
|
Carsten, meanwhile has put CIDER under BSD license (see https://embedded.eecs.berkeley.edu/pubs/downloads/cider/index.htm). Together with ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change this means that CIDER is covered by the modified BSD, which is compatible to DFSG. Holger An update to the license list: ngspice licenses All ngspice files are covered by the 'New BSD' (3-clause BSD) except for: ngspice/doc SPICEDOC, not compatible to DFSG considered outdated ngspice/contrib various, considered outdated ngspice/m4 ?, compatible to New BSD ngspice/src/tclspice.c LGPLv2 all files in ngspice\src\maths\sparse unnamed MIT license, compatible to New BSD ngspice/src/spicelib/devices/adms/ekv ngspice/src/spicelib/devices/adms/hicum0 ngspice/src/spicelib/devices/adms/hicum2 ngspice/src/spicelib/devices/adms/psp102 copyright info, but no license information given ngspice/src/spicelib/devices/adms/mextram Educational Community License version 1.0 ngspice\src\spicelib\devices\adms\admst LGPLv2.1 ngspice\src\spicelib\devices\ndev public domain ngspice\src\spicelib\devices\hisim2 ngspice\src\spicelib\devices\hisimhv1 ngspice\src\spicelib\devices\hisimhv2 unnamed Hiroshima University and STARC license, compatible to New BSD ngspice\src\xspice public domain except for ngspice\src\xspice\icm\table\ GPLv2 or newer ngspice\src\frontend\numparam LGPLv2 or newer ngspice manual (https://sourceforge.net/p/ngspice/ngspice-manuals/ci/master/tree/) Creative Commons Attribution Share-Alike (CC-BY-SA) v4.0 My personal recommendation on what to do to obtaim a DFSG compatible build would be: Skip the following: all files in ngspice/doc all files in ngspice/contrib all files in ngspice\src\spicelib\devices\adms\ Check if Hiroshima University and STARC licenses are compatible to DFSG So finally adms would not be available. For KiCAD users this would be of absolutely no concern. |
|
From: Carsten S. <c.s...@t-...> - 2018-03-17 13:19:52
|
Hello Holger, Am 17.03.2018 um 11:28 schrieb Holger Vogt: > Carsten, > > meanwhile has put CIDER under BSD license (see > https://embedded.eecs.berkeley.edu/pubs/downloads/cider/index.htm). > Together with > ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change this means > that CIDER is covered by the modified BSD, which is compatible to DFSG. sounds good! Thanks all people who are involved to make this possible! Are there plans to release a ngspice-27.1 tarball with these license changes? I've worked the last weeks on packaging KiCad5-rc1 and it's now living in Debian experimental. I plan now to work (again) on the ngspice packaging, thanks to the previous answer from Robert and some more viewing on existing Tcl related packages in Debian it's now more clear how the packaging should be done. -- Regards Carsten Schoenert |
|
From: Holger V. <hol...@un...> - 2018-06-01 20:33:12
|
Carsten, ngspice-28 is available. All files in the tar ball have a license comptible to DFSG. Holger |
|
From: Carsten S. <c.s...@t-...> - 2018-06-02 04:48:45
|
Hello Holger, Am 01.06.2018 um 22:33 schrieb Holger Vogt: > Carsten, > > ngspice-28 is available. > All files in the tar ball have a license comptible to DFSG. this sounds really great! I've noticed this already last week or so as I looked into the recent source. Thank you all who have made this possible! I wasn't aware this would be possible and happen in that short amount of time, this brings in we don't need two source packages in Debian and I can just use the existing one but need to move my work now on top of that. I will start to work an this over the weekend now KiCad is already uploaded to unstable. :-) -- Regards Carsten Schoenert |