Bug#741258: libphonenumber packaging
-----BEGIN PGP SIGNED MESSAGE-----
On 27/05/14 15:59, tony mancill wrote:
> On 05/26/2014 10:38 AM, Daniel Pocock wrote:
>> Hi Laurent,
>> I use libphonenumber too (it is in Lumicall, for example)
>> Has anybody else responded about packaging it or did you start on
>> it yourself?
>> I notice upstream has debian/ artifacts in the repository:
Can anybody comment on whether this is consistent with the current
>> packaging standards for debian-java?
> Hi Daniel,
> The answer about packaging standards and whether the package could
> enter Debian is "no, but it's a decent start." I was able to get
> it built, noting the following.
> * it has a build-dep on libre2-dev, which is currently only in
> * it is currently a native package, but should be easy to convert
> * it's missing build-deps on: libboost-system, junit, ant-optional
> * I had to edit the CMakeLists.txt to add "system" as a Boost
> * the resulting -java and -dev debs look okay, but the actual
> runtime deb is empty (no .so files)
> * the build modifies one of the source files, and creates a few new
> It would be nice to have something that links against it to test
Tony, thanks for all this feedback
Fredrik indicated upstream would welcome improvement to the packaging
I don't mind helping out with this and I can potentially pull out some
of the code from Lumicall to provide a test case for the Java side of
this. I can imagine a project like Jitsi using it to handle "tel:"
I'm wondering if it should be maintained by simply mirroring/cloning
the upstream repository or by building a Git repository with
git-import-orig from the upstream source tarball?
Fredrik, do you foresee moving from SVN to Git any time soon? If not,
I may set up a git mirror (I have a script that does this and keeps
them in sync) and then I can make changes on a branch more easily.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
-----END PGP SIGNATURE-----