Hi Raphael,
Raphael Hertzog wrote:
> this is a clear design choice of upstream and given that all those
> libraries are maintained by the same person (and that he is not providing
> any official API stability), I don't think it's really problematic.
> Also all those libraries are really small.
>
Hello,
> I vaguely recall discussions about libbfio at some point.
Probably this discussion
https://lists.debian.org/debian-security-tools/2020/12/msg00012.html ;)
Regards,
Aleksey
* Raphael Hertzog:
> I don't have any reference to give but I remember that we already
> had this discussion once on the pkg-security list, possibly during a
> review of one of those packages.
I vaguely recall discussions about libbfio at some point.
Cheers,
-Hilko
Hi Axel,
this is a clear design choice of upstream and given that all those
libraries are maintained by the same person (and that he is not providing
any official API stability), I don't think it's really problematic.
Also all those libraries are really small.
Trying to package them separately wo
Hi,
I'm not yet writing bug reports about this because this is a rather
huge matrix of things which are bad and I suspect I haven't found all
of this type.
While working on plaso and updating dependencies of it which are too
old for plaso's most recent release, I noticed that e.g. the libevtx
sou
