Hi Lin, I am sorry, but the package in the current state is nowhere near to be released in the Debian.
The upstream tarball includes two upstream libraries. That might be okayish for releasing just the client, but when you package other binaries (the server) which will link to the same library, you want to use shared libraries. Also this makes the packaging unnecessarily complex. But you certainly cannot embed libjson-glib-1.0 as part of libsearpc (under different name), that's just security nightmare I will create the initial packaging in correct way (I already have libsearpc 1.1.0+dfsg, e.g. without embedded json-glib, packaged), and make you the co-maintainer of the packages. Ondrej On Wed, May 22, 2013 at 2:09 PM, Shuai Lin <linshuai2...@gmail.com> wrote: > Hi Sury, > > Glad to hear this. Actually I have been working on packaging > seafile-client for debian with guide and help from Jérémy Lal < > kapo...@melix.org>, who has been very nice and patient. > > But for the last two months Jeremy seems to be kind of busy, so the debian > related work has been stalled for a while. > > Since you are interested, here are some work we have done: > > The seafile "deb" branch on github: > > https://github.com/haiwen/seafile/tree/deb/debian > > "seafile-client" package on mentors.debian.net > > http://mentors.debian.net/package/seafile-client > > > Regards, > Lin > > > > On Wed, May 22, 2013 at 7:50 PM, Ondřej Surý <ond...@sury.org> wrote: > >> Hi, >> >> I am interested in building seafile, seahub and client packages for >> Debian. Did you already do some work or it this more like RFP than ITP? >> >> Ondrej >> -- >> Ondřej Surý <ond...@sury.org> >> > > -- Ondřej Surý <ond...@sury.org>
