path: root/debian/libfuzzylite5.1.lintian-overrides
diff options
authorJohannes Schauer <>2015-07-07 11:12:00 +0200
committerJohannes Schauer <>2015-07-07 11:12:00 +0200
commitd210b3addc8ffed7214afd8c7882e700fbcc38c5 (patch)
treeded15607f7f24f83d2d0d7c542265c0a97af577a /debian/libfuzzylite5.1.lintian-overrides
fuzzylite (5.1+dfsg-1) unstable; urgency=medium
* new upstream version (Closes: #777858) * removed debian/patches/20140705-minor-improvements-on-building-script as upstream integrated it. Adjust build options in d/rules accordingly. * delete debian/patches/20140714-building-from-objects-just-once and debian/patches/20141027-fix-some-spelling as they have been applied upstream * install usr/lib/*/pkgconfig/fuzzylite.pc in fuzzylite-dev * SONAME bump from 5.0 to 5.1, so renaming libfuzzylite5.0 to libfuzzylite5.1 * add debian/patches/pkgconfig_installdir to install pkgconfig file in correct location # imported from the archive
Diffstat (limited to 'debian/libfuzzylite5.1.lintian-overrides')
1 files changed, 10 insertions, 0 deletions
diff --git a/debian/libfuzzylite5.1.lintian-overrides b/debian/libfuzzylite5.1.lintian-overrides
new file mode 100644
index 0000000..ed9cc6f
--- /dev/null
+++ b/debian/libfuzzylite5.1.lintian-overrides
@@ -0,0 +1,10 @@
+# In the words of the author of fuzzylite, Juan Rada-Vilela:
+# The calls to exit() happen on static methods signalHandler and terminate, both
+# of which are optionally configured by the program, not the library. The library
+# will not use either of these methods unless a program explicitly asks these
+# methods to be used. These are just handy/example methods. I would expect
+# programs to provide their own handling of signals instead.
+# See:
+libfuzzylite5.0 binary: shlib-calls-exit