In the 2.0 release the libs are shared only by the applications and external users will not be able to depend on forward compatibility of the libraries as shipped in 2.0
There are several things in the KOffice libraries that have to be renamed/deleted and generally cleaned up before we can make the libs become binary+source compatible in future features. Lets keep a list of things on a Refactor Todo page.
GPL code in LGPL libs/ dir: obtained using grep -lR "GNU General"|grep -e '\.h$' -e '\.cpp' -e '\.cc'|grep -v -e test -e benchmarks -e parser. Please remove items from the list when fixed.
Maybe also this - GPL code in filters/ dir:
libmso/msodraw.h libmso/msoleps.h libmso/shapes2.cpp sheets/qpro/libqpro/qpro/common.h sheets/qpro/libqpro/qpro/formula.h sheets/qpro/libqpro/qpro/record_factory.h sheets/qpro/libqpro/qpro/record.h sheets/qpro/libqpro/qpro/stream.h sheets/qpro/libqpro/qpro/tablenames.h sheets/qpro/libqpro/src/formula.cc sheets/qpro/libqpro/src/record.cc sheets/qpro/libqpro/src/record_factory.cc sheets/qpro/libqpro/src/stream.cc sheets/qpro/libqpro/src/tablenames.cc words/msword-odf/conversion.cpp words/msword-odf/conversion.h words/msword-odf/document.cpp words/msword-odf/document.h words/msword-odf/drawclient.cpp words/msword-odf/exceptions.h words/msword-odf/graphicshandler.cpp words/msword-odf/graphicshandler.h words/msword-odf/msdoc.h words/msword-odf/mswordodfimport.cpp words/msword-odf/mswordodfimport.h words/msword-odf/paragraph.cpp words/msword-odf/paragraph.h words/msword-odf/tablehandler.cpp words/msword-odf/tablehandler.h words/msword-odf/texthandler.cpp words/msword-odf/texthandler.h words/msword-odf/versionmagic.h words/msword-odf/wv2/src/associatedstrings.h words/msword-odf/wv2/src/properties97.cpp words/msword-odf/wv2/src/styles.cpp words/msword-odf/wv2/src/textconverter.cpp words/msword-odf/wv2/src/ustring.cpp words/msword-odf/wv2/src/utilities.cpp words/msword-odf/wv2/src/word95_generated.cpp words/msword-odf/wv2/src/word95_helper.cpp words/msword-odf/wv2/src/word97_generated.cpp words/msword-odf/wv2/src/word97_helper.cpp words/msword-odf/wv2/src/word_helper.cpp words/msword-odf/wv2/src/wv2version.cpp
Minified js files are considered compiled files in Debian, and require source code (the non minified js) to produce the minified/compiled file on package build.
We're concerned about license for these profiles. In some cases, neither licensing nor copyright is clear. Metadata is helpful, but not enough. Public domain profiles are ok, but there must be a way to verify it. For instance: download url where the authorship/license is stated.
If color profiles (as binary file) are generated from a human readable source, then having source (with licensing information) would be helpful as well.
Note: I used iccdump from debian package argyll to get profile metadata. (argyll package is https://packages.debian.org/sid/argyll )
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 from 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, but 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.
These are binary files which should be avoided in an upstream tarball if possible. 3rdparty/google-breakpad/src/client/mac/gcov/libgcov.a 3rdparty/google-breakpad/src/third_party/linux/lib/glog/libglog.a 3rdparty/google-breakpad/src/third_party/linux/lib/gflags/libgflags.a 3rdparty/google-breakpad/src/tools/windows/binaries/symupload.exe 3rdparty/google-breakpad/src/tools/windows/binaries/dump_syms.exe
References: http://lists.kde.org/?l=calligra-devel&m=141409908920334&w=2 (From Raúl Sánchez)