Re: Bug#807968: RFP: haskell-gitlib-libgit2 -- Libgit2 backend for gitlib (haskell)

[Dmitry Bogatov <KAction@gnu.org>]

On 2015-12-20, Joachim Breitner <nomeata@debian.org> wrote:
> Am Donnerstag, den 17.12.2015, 20:59 +0000 schrieb Dmitry Bogatov:
>> On 2015-12-14, Joey Hess <id@joeyh.name> wrote:
>> > Package: wnpp
>> > Severity: wishlist
>> >=20
>> > * Package name=A0=A0=A0=A0: haskell-gitlib-libgit2
>> > * URL=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0: http://hackage.haskell.or=
> g/package/gitlib-libgi
>> > t2
>> > * License=A0=A0=A0=A0=A0=A0=A0=A0=A0: BSD
>> > =A0 Programming Lang: haskell
>> > =A0 Description=A0=A0=A0=A0=A0: Libgit2 backend for gitlib (haskell)
>> >=20
>> > * https://github.com/jwiegley/gitlib/issues/43
>> > =A0 The version of libgit2 bundled with hlibgit2 is currently 0.18,
>> > =A0 which is older than the versions in Debian. This may make it hard
>> > =A0 to build the package against the system libgit2. (Haven't tried.)
>>=20
>> I investigated a bit. It is really complicated. Version of libgit2 in
>> sid is 23, which is source-incompatible with 18.
>>=20
>> Enumerations fields gets added/removed, whole structs gets removed,
>> callback arguments are changed and so on. It is only things I
>> encountered in attempt to compile, to say nothing about properly
>> mirroring libgit2-23 API. It needs not patch, but support from
>> maintainer, if you ask me.
>>=20
>> Sorry, but I am not up to this migration.
>
> if it is too hard, is it reasonable to simply use the embedded library
> code?

As far as I know, it violates Policy, isn't it?

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
X-Web-Site: sinsekvu.github.io