debian packages for silc-client 1.0.4.1 (for etch)

[Daniel Kahn Gillmor]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey good people--

i've bumped along the old packaging from silc-client to make .debs for
version 1.0.4.1.

They're available in the same place the old ones were, and they should
have the following sha1sums:

782b577fc59415c6022f4a00c81270d15ab263fe  silc-client_1.0.4.1-1.diff.gz
a254cb3f9b8625a5a36a4faf599d6020bebaf8cd  silc-client_1.0.4.1-1.dsc
7db8053b0fc5bff3eb4c82b91d21702031e7d487  silc-client_1.0.4.1-1_i386.build
3be7fef59265a7f3991beecd9f92fceef68eca70  silc-client_1.0.4.1-1_i386.changes
1137daf8810bd7da368ec726ad9bd3edba78a89b  silc-client_1.0.4.1-1_i386.deb
2f2ced79882f5f12e4a4e3ea1f8daa21e5609dd6  silc-client_1.0.4.1.orig.tar.gz

They're built against debian etch, which is now debian's stable
release.

I'm still not happy with the packaging strategy: there's too little
code reuse and library reliance for my taste.

I'd like try to package silc-client 1.1 (when it comes out) with a
proper packaging strategy, which should include:

 * making it depend upon a modern version of the silc-toolkit package,
   which is currently out of date in debian.  (debian bug #413790 [0],
   if anyone wants to add weight to the bug by commenting on it)

 * building a silc-plugin package which depends on irssi, so that
   irssi users can simply add the silc module to irssi and work from
   there.

Given the monolithic nature of the silc-client source tarball (it
appears to include the silc toolkit and large chunks of irssi), i'm
not sure what the best way to strip out this code duplication is.
Suggestions are welcome.

I'd also like to rebuild the silc-server packages so that they depend
on a modern silc-toolkit library, instead of including the library
sources directly.  Again, given the monolithic nature of the source
tarball, i'm not sure how to do this cleanly.

I'd really like to see silc (both client and server) available by
default for all debian (and debian-derivative) users.  Any advice or
suggestions for packaging needs would be welcome.

            --dkg

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413790
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGGwfSiXTlFKVLY2URApZyAKD97ctRaayzM/2+AoDGc2GZgu91RACbBi1I
Em+tMhv5GWW/Sq5SlwtVUJc=
=1r/X
-----END PGP SIGNATURE-----