[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Status of libsonlib



Hi Shayan,

you asked about the packaging status of libsonlib since you need it for
marginphase.  I pushed something which somehow creates some binary
package containing some header files and a static library.

It builds if you uncomment the building of libquicktree-dev[1]
(or just checkout commit fe426a6598742190616d848b8a06773b570106f1)

However, the libsonlib packaging is not yet "sensible" in the
following ways:

1. There are installed some binaries under /usr/bin which seem to be tests only.

   While the build time test works the autopkgtest is just a pure
   boilerplate == non-functional.

   I think the way to finalise libsonlib would be to find out whether
   there are any sensible binaries in /usr/bin and leave these (if
   they are not just tests) and may be write some manpage (using
   help2man - no real effort to write it manually!)

2. Inside the autopkgtest reproduce compiling the test tools and run
   the tests.


I stopped for the reason that my original target signalalign needs a further dependency:

   https://salsa.debian.org/med-team/python-servicecourse

This should be a proper Python Module but upstream has just thrown
three files into the root dir of the archive.

Possibly this can be fixed by some simple setup.py to profit from
pybuild - but may be moving those files manually might be possible as
well.  I simply stoped here and since my final target signalalign
seemed to complex I left sonlib as well since I was not sure whether
the packaging finally works that way.


If you have some other target that needs libsonlib it would make
perfectly sense to continue that effort and check whether that
target builds with the current libsonlib - if not fix it. ;-)

Kind regards

      Andreas.


[1] https://salsa.debian.org/med-team/quicktree

-- 
http://fam-tille.de


Reply to: