Hi Matthias,
On Tue, Feb 28, 2017 at 11:16:37AM +0100, Matthias Klumpp wrote:
> > I'd fully trust your insight here but I admit Meson is totally new to me
> > and crafting a Meson control file for a library without having any idea
> > about D is a bit over my current status of knowledge. So I either need
> > to use what upstream provides or ask here for help.
>
> D is really easy to write if you know a bit of C and maybe Python or Java ^^
> Writing a Meson build definition is trivial too, I can write on for
> this project if you want and submit it upstream.
It would be helpful if you could provide a Meson build definition and
I'd happily submit it upstream.
> > I admit I have no idea how to do this. Its the first time I see D code
> > at all. May be it would be even better if the Debian D team could
> > package BioD which I need for some other package as a pre-dependency.
>
> I'd rather not want that to happen - the D team is currently mostly me
> (and Markos), and packaging a library which we don't use is a bad
> idea. I have too many packages already and I fear I will not be able
> to adequately maintain them if I have too many and don't even use
> them.
That's OK.
> However, I could help with the packaging. I'll see whether BioD is
> easy to port away from std.streams (doesn't look like it
> unfortunately) and if not I could supply Meson build definitions to
> the projects.
The libbiod Git repository[1] is writable for every DD - so if you
would like to commit something there that would be really welcome.
> Is BioD a normal shared library? What are you doing with it?
My final target (actually also a predependency for another target)
is sambamba[2] which using BioD as a git subrepository to build.
Kind regards
Andreas.
[1] https://anonscm.debian.org/git/debian-med/libbiod.git
[2] https://github.com/lomereiter/sambamba
--
http://fam-tille.de
