Hi, On 9 May 2018 at 02:15, Nicholas D Steeves <nstee...@gmail.com> wrote: > Package: src:btrfs-progs > Severity: normal > Tags: patch > > Attached is a patch that will allow btrfs-progs-4.16.1 to be built on > Debian and Ubuntu. AFAICT there's no need to add --with python3 at > this time, but I'm guessing that some day that might become a good > idea.
I have started on packaging 4.16.1 as well. And i would NAK this for now. It seems like btrfs-progs upstream makefiles are buggy. It tries hard to create dynamic & static binaries, and libraries, however, neither libtrfs nor libtrfs-utils libraries are dynamically linked to the btrsfs-* utils. Thus at the moment, it looks like nothing links to btrfs.so, althought everything could have been linked to it. I'm not sure what the upstream intention is/was for the btrfs.so - is it internal only library, which should then be noinst; or is it meant to be a public library, yet private, as in libbtrfs.so.0 without any public -dev package; and similarly what to do about btrfs-util.so and the python bindings. Thus I was going to seek upstream clarification on wether or not btrfs & btrfs-util libraries are meant to be public or private; and installed or not. I wonder if this is the result of not using automake =/ -- Regards, Dimitri.
