On Monday, 10 April 2017 at 11:40:12 UTC, Matthias Klumpp wrote:
Recompiling the dependency-chain of a software from source when
compiling a package using the "right" compiler and statically
adding the code is forbidden by distro policy.
This is the part that I do not understand.
Who came up with those policies and decided that they apply to D?
Because I really don't think they should.
A lot of D code is generic. Very extremely few exceptions, it is
a given that any time a library is used, at least some part of
the library's code is going to be compiled not when the library
is "built", but when programs using the library are. The notion
of D libraries preserving ABI compatibility of built shared
libraries is pretty much unheard of (it would have to be an
explicit design goal), with Phobos and everything else going for
source-compatibility only. Heck, there are packages out there
that do not even produce useful object files (such as header-only
C++ libraries).
As far as I can see, the main obstacle of D in Debian is the
extreme dogmatism of the distribution's policies. D is not C
(where these rules make much more sense), so I really don't think
the same rules should apply. Can we treat it more like an
interpreted language instead?
