Hi Matthias,

On Wed, Jul 26, 2017 at 05:56:44PM +0200, Matthias Klumpp wrote:
> >
> > debian/patches/01_meson-build.patch.patch file
> >
> > +undead_lib = shared_library('undead',
> 
> You should really use library() instead, hardcoding shared_library
> makes no sense here:
> http://mesonbuild.com/Reference-manual.html#library
> 
> > works
> > http://mesonbuild.com/Porting-from-autotools.html
> >
> > I think for now binNMUing is fine, but in the future splitting the package, 
> > and add that
> > library shared is preferred (but please talk to D people, and try to 
> > understand how much
> > the ABI is stable
> 
> The ABI is not stable at all. It's not completely broken each release,
> some bits have been stable for a long time, but you can never be sure
> since upstream gives no ABI stability promises.
> If the D software is using the D runtime and/or standard library, you
> get rebuilds for free, since the dependency on the standard library
> will be versioned and a rebuild will be needed to switch to a new
> release.
> If D a D library is not using the runtime (a rather rare event,
> usually happens for very close-to-metal stuff, where having a GC and
> the extra weight of the runtime is not desired), then you're on your
> own at the moment, as we haven't implemented anything in Debian yet
> that could detect this case and ensure transitions happen properly.
> 
> The undead library falls into the simple category though, as it
> depends on both the runtime and the standard library.

I admit your explanation was interesting in general but I have no idea
what practical implications it has to fix this bug.  In short:  I have
no idea what to do now.

Kind regards

       Andreas.

-- 
http://fam-tille.de

Reply via email to