summaryrefslogtreecommitdiff
path: root/libfuzzylite5.1v5.lintian-overrides
diff options
context:
space:
mode:
authorGianfranco Costamagna <locutusofborg@debian.org>2016-08-13 14:33:03 +0100
committerGianfranco Costamagna <locutusofborg@debian.org>2016-08-13 14:33:03 +0100
commit59fd708e8df2286bf221956d702e9c7c0e71bc5d (patch)
treede51c1457cf1363db79d0c83aaac49fe62819a03 /libfuzzylite5.1v5.lintian-overrides
Import fuzzylite_5.1+dfsg-3.1.debian.tar.xz
[dgit import tarball fuzzylite 5.1+dfsg-3.1 fuzzylite_5.1+dfsg-3.1.debian.tar.xz]
Diffstat (limited to 'libfuzzylite5.1v5.lintian-overrides')
-rw-r--r--libfuzzylite5.1v5.lintian-overrides10
1 files changed, 10 insertions, 0 deletions
diff --git a/libfuzzylite5.1v5.lintian-overrides b/libfuzzylite5.1v5.lintian-overrides
new file mode 100644
index 0000000..fdda54a
--- /dev/null
+++ b/libfuzzylite5.1v5.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: https://github.com/fuzzylite/fuzzylite/issues/4
+libfuzzylite5.1v5 binary: shlib-calls-exit