Re: libphonenumber packaging
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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?
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741258
>>
>> I notice upstream has debian/ artifacts in the repository:
>> https://code.google.com/p/libphonenumber/source/browse/trunk/debian
>>
>>
>>
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
> experimental
>
> * 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
> component.
>
> * 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
> ones.
>
> It would be nice to have something that links against it to test
> with.
>
Tony, thanks for all this feedback
Fredrik indicated upstream would welcome improvement to the packaging
files.
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:"
URIs too.
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.
Regards,
Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJTh3/kAAoJEOm1uwJp1aqD5I0P/iO2jI43/FRj1jA62U0iCur7
pOQC2j06ixdPzMwCG9jxCmZT1zNwVoGDjJ6SI9hPKsu92SlbUpuWyqX/3dqfPrx3
nCf0hrVtXm795NdZVW4cpPLYwocDSNvHzOoqrhcNlS8oPA2uDwiodEyThGU946LG
NBe0VZdt+//Oaspp8QhbxfhrpUIkfD7Nkfj4hyhYGT1OkUdRXkfnQYcrkBwJJtAo
y8ZZzwZMzPuSZUQ7BIm0oQlanEOhmb4L3Vc2g5kBLPcT0qNJx0n6LxvetwQFYR8v
bV1N25SQ/P4HCEkkJLfo7BxT1Drw3a8CvzWhZuvRVnMioMnjMNjPnAQBHDl7WlAp
xReEYDoqneKatyOK12x8HqCRJPKh7//GmuKSX/RafqJQ1LLiOdP0uQ6Nx+YKwvD+
KWdS3zLhk8c+h3HVImcuPytDUOzcoxeHkpwArP7lNVi7hc2xCk0rkpCa/UJUF4tY
g9doZ64Vvjr9/f0ERnweSwbi5MsAVNsv42xS5LrR5T4hbxb3aadSXXrSOrvGjuAO
GH4UFyAn3J0xPOoheszcYBGZMEg0y00DJPsRnJg1Pve+QPR9rhAOnGooXUs91zB2
O6Fh9gqAvwzUhldo//gU1smMseJqtznYhhIafGJOMNXY7qqNs32A9VhuqwcP/FTm
DhZPvQxypZt+nH257aLC
=UTfb
-----END PGP SIGNATURE-----
Reply to: