Re: radare2-cutter initial upload; possible radare2 update?

[Hilko Bengen]

* Sebastian Reichel:

>> I'd like to give both a shot.
> Sure go for it. IIRC they were removed when they were no longer
> required for bokken.

All I have achieved for radare2-bindings so far is finding and
diagnosing a RC bug in valabind. :-(

Given upstream's suggestion to use the r2pipe interface with JSON
output, I'm not going to pursue this for now...

About r2pipe... I'm no longer sure about those seemingly trivial
implementations.

Cheers,
-Hilko

Re: radare2-cutter initial upload; possible radare2 update?

[Sebastian Reichel]

Hi,

On Sat, Jan 26, 2019 at 12:32:28AM +0100, Hilko Bengen wrote:
> * Sebastian Reichel:
> 
> > Thanks, for taking care of this. I'm currently a bit short on time.
> > I noticed, that you enabled OpenSSL, which is not ok. 
> 
> Right. Will revert that right away, now that my upload has been accepted
> into unstable.
> 
> > Also I think we should switch to upstream soname (3.2.1), which plains
> > the way to use meson instead of their own build system.
> 
> As long as upstream keeps their ABI stable across patchlevel releases,
> I see no reason for doing that.

upstream does not guarantee any ABI stability. This needs to be checked
downstream (i.e. the maintainer importing the updated release).

> Couldn't we also override the soname picked by the meson
> buildsystem?

I think that requires patching the build system. FWIW I rebased my
meson patch on top of your changes and pushed it into an extra
branch:

https://salsa.debian.org/pkg-security-team/radare2/tree/meson

It works, but uses upstream's soname.

-- Sebastian


signature.asc
Description: PGP signature

Re: radare2-cutter initial upload; possible radare2 update?

[Hilko Bengen]

Hi Sebastian,

what do you think about re-introducing the radare2-bindings package and
packaging r2pipe?

I'd like to give both a shot.

Cheers,
-Hilko