[Pkg-crosswire-devel] Progress: sword 1.5.11-based package now available in my PPA, please test it!

[Jonathan Marsden]

Daniel Glassey wrote:

> On Sat, Jan 24, 2009 at 10:03 PM, Jonathan Marsden <jmarsden at fastmail.fm> wrote:

> Great work :)

Thanks!

> debian/rules
> DEB_DH_MAKESHLIBS_ARGS_libsword6 := -V"libsword7 (>= 1.5.11-1)"
> DEB_SHLIBDEPS_INCLUDE_libsword6 := debian/tmp/usr/lib
> 
> that should be DEB*_libsword7

Yes.  Among all those 6 becomes 7 edits, I missed a couple!  Can you
explain why we need the (>= 1.5.11-1) type of qualifier at all?  What
purpose does it serve?  Is there documentation on using these variables
somewhere that I should have read?  Also, doesn't this duplicate what
libsword7.shlibs does??  As you can tell, I'm probably a bit muddled
about how this stuff works.  Can you educate me?

> I think one of the complaints somewhere was that the lib wasn't built
> with icu support enabled so let's add the configure option --with-icu
> which is off by default

Yes.  I wanted to try a "get it to build at all" package first, and then
start on Refdoc's list of requests (except I moved the CGIs, because
that was so trivial and I'm somewhat security-aware).

> debian/diatheke.README.Debian
> I've never tried this but that is my best guess of what to name the
> file to be a README.Debian just for the diatheke package

Yes; I was hoping someone else might volunteer to write the text, but
I'll just go ahead and do it.

> debian/control
> package libsword7 should 'Replaces' libsword6

Should it really?  That was a topic I was going to ask you about!  Can't
these two binary packages coexist?  Imagine a system where there is an
older GnomeSword installed; you don't want to break it by installing a
new diatheke and its new libsword7 dependency, and there is no need to
so break it, is there?  Surely the whole point of having differently
named libswordX packages is so that they *can* coexist, allowing apps of
variying ages that depend on different binary-incompatible versions of
the library to coexist on one machine?  Am I missing something here?

> diatheke - let's change the Recommends of apache2|https to Suggests

Actually, now we're not installing any CGI code at all, let's just
remove it completely!

> debian/copyright
> let's update the copyright date to 2009

OK, can do.  Upstream does not seem to have done so, though.  Their
LICENCE file shows 1996-2006, and I see nothing with a 2009 copyright in
the 1.5.11 source tarball at all.  The usual expectation is to copy the
upstream copyright notice to debian/copyright, isn't it?  Should
packagers really be changing/correcting legal documents created upstream??

> debian/diatheke.dirs
> we can remove usr/lib/cgi-bin since we aren't installing anything there now

Actually we can remove much of the .dirs stuff, I am almost sure...
usually you only need debian/*.dirs for installing empty directories,
dh_install will do the right thing automatically for directories it
installs files into, unless I am very confused... which is possible!
I'm going for a "minimalist" aproach on ./dirs files this next time,
let's see what breaks!

> debian/libsword7.shlibs
> I think that should be
> libsword 7 libsword7 (>= 1.5.11-1)

Probably: again, can you please explain what this is really doing for us
-- what breaks if we delete that debian/libsword7.shlibs file, and why
is this info both here and in debian/rules ?  The examples in the
dh_makeshlibs man page do not include the -n suffix, BTW.  I strongly
suspect we can remove debian/libsword.shlibs and let the rules file and
dh_makeshlibs "do the right thing" for us... can you confirm that?

> debian/libsword-dev.dirs
> I think these dirs should be added
> usr/include
> usr/include/sword
> usr/lib/pkgconfig

See my comment above about dh_install doing this for you... we should
definitely check on this, since we are apparently looking at the use of
debian/*.dirs (and to a lesser extent debian/*.shlibs) differently!

For this kind of rapid dialogue (which is really good to have!), maybe
we should be using IRC... I'm in #sword on Freenode right now (my nick
is jmarsden) ...

Jonathan