diff options
author | Johannes Schauer <josch@debian.org> | 2015-10-25 22:15:35 +0100 |
---|---|---|
committer | Johannes Schauer <josch@debian.org> | 2015-10-25 22:35:26 +0100 |
commit | f327338654a7266c92961e075ad60b173d3d5861 (patch) | |
tree | c110550ada7d842b8d65867b2f74535af044c5bd /debian/libfuzzylite5.1v5.lintian-overrides | |
parent | d210b3addc8ffed7214afd8c7882e700fbcc38c5 (diff) |
release 5.1+dfsg-2debian/5.1+dfsg-2
Diffstat (limited to 'debian/libfuzzylite5.1v5.lintian-overrides')
-rw-r--r-- | debian/libfuzzylite5.1v5.lintian-overrides | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/debian/libfuzzylite5.1v5.lintian-overrides b/debian/libfuzzylite5.1v5.lintian-overrides new file mode 100644 index 0000000..fdda54a --- /dev/null +++ b/debian/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 |