[med-svn] [libundead] 01/01: Add reasons why only static lib will be provided.

[Andreas Tille]

This is an automated email from the git hooks/post-receive script.

tille pushed a commit to branch master
in repository libundead.

commit cdbc319bd2fbb3349f1c8f1338af04840ddd4998
Author: Andreas Tille <tille at debian.org>
Date:   Fri Mar 3 15:55:03 2017 +0100

    Add reasons why only static lib will be provided.
    
    Signed-off-by: Andreas Tille <tille at debian.org>
---
 debian/README.source | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 0000000..04951f3
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,18 @@
+Some reasoning to stick to static library only is given here:
+
+   https://lists.alioth.debian.org/pipermail/pkg-d-devel/2017-March/000192.html
+
+which is summarised to:
+
+   D upstream provides to ABI guarantees at all, so with every new compiler
+   release, the ABI of binaries could change. With static libraries, we get
+   build failures then, with shared libraries users will have runtime
+   failures (unless one maintains a symbols control file, which is less fun
+   with D).  Additionally, libraries built with GDC won't work with LDC and
+   vice versa. At time, all D shared libraries are explicitly built with
+   LDC, so inside Debian this is not an issue.
+   
+   So, in summary: Every D shared library without a symbols control file
+   is potentially dangerous. If you want to build a shared lib for undeaD
+   regardless, it's as easy as changing static_library to library in
+   meson.build.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-med/libundead.git