From calligra-devel Sun Jan 04 16:06:26 2015 From: Jos van den Oever Date: Sun, 04 Jan 2015 16:06:26 +0000 To: calligra-devel Subject: Re: How to generate mso.jar (Re: Calligra licensing and copyright bits) Message-Id: <1858195.4CfZk6j1Cx () joga> X-MARC-Message: https://marc.info/?l=calligra-devel&m=142038760119427 On Sunday 04 January 2015 02:04:09 Friedrich W. H. Kossebau wrote: > Am Donnerstag, 23. Oktober 2014, 23:17:48 schrieb Ra=FAl S=E1nchez Siles: > > Hi: > > = > > As a Debian maintainer of the calligra package, I'm reviewing licensing > > and > > copyright details. We've found some issues that I'll explain in this em= ail > > and we'd like to hear your point of view. > = > > = > > Java jar files > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > jar files are binary files, as such, in Debian we need the source code = of > > those files and generate them on package build (or removing the files f= rom > > the tarball and adding dependencies on the packages that provide these > > files). > > = > > In the jar case, there are some pointers on where the jar comes from, b= ut > > still bundling a generated binary is not desirable. > > = > > The fixes for that from the licensing point of view are: > > - Removing the feature > > - If the jar generates code needed at build time, adding the required > > (source) files which are generated from the jar. But not the jar. Also > > include a script or document a procedure how to get those files. > > - If the jar is required as a runtime dependency, you could either add a > > run time dependency on a separate package providing that jar or generate > > the jar at build time. > > = > > filters/libmso/generated/mso.jar > > = > > As per README in that directory this jar generates some code that's u= sed > > = > > later. > > PROPOSAL: Describe (or script) the procedure to generate the code and > > remove the jar file. > = > The README refers to http://www.gitorious.org/msoscheme as the source of > mso.jar. Which still exists (good) and seems to be basically done by you, > Jos, once upon a time at least. Just, there is no README there and, worse, > also no obvious license for msoscheme. > And for recursive fun for the good Debian License checking people there is > another binary blob inside those sources, from poi.apache.org ;) I've added a Readme.md with license information for MSOScheme and POI to th= e = repository of MSOscheme now. https://www.gitorious.org/msoscheme/msoscheme/ The POI code is only there for testing the generated java code. This is not = used by Calligra at all. I have updated MSOScheme: it now writes the version of MSOScheme into the = generated files. The version contains the sha1. So it is always possible to = find the exact version of MSOScheme to recreate the files simpleParser.h an= d = simpleParser.cpp. This means the mso.jar does not need to be part of the = Calligra source code any more. I put up a review request to add the better documentation to calligra. https://git.reviewboard.kde.org/r/121837/ If the mso.jar should not be part of the Calligra repository, then it shoul= d = be replaced by mso.xml. Cheers, Jos _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel