[Pkg-silc-devel] Bits from DebCamp - Binary package names

[Jérémy Bobbio]

Hi!

I am in Edindburgh since last Saturday and took the opportunity of
DebCamp to work on SILC packages.

I have made more progress on rewriting silky.  It is still not finished,
but there is definitely some progress going on.  The code base is
starting to look sane, most internal API are converging to something
loooking good.  I'll continue to work on that next weeks.

I started to package silc-server from a prerelease [1].  Packaging
silc-server proprely needed quite some work, as it involves debconf,
ucf, tricky posinst script and spliting upstream configuration file.

[1] http://silcnet.org/priikone/pre/silc-server-1.1-pre1.tar.gz

I will surely upload a first version of this package by the end of
tomorrow.

Packaging silc-server made me think on how the resulting binary package
should be called.  Usually package names ending with "-server" are
virtual packages provided by different softwares.  In the hope to see
more development around SILC happening in the future, I think we should
also follow this trend.

In this case, the source package "silc-server" would produce a binary
package named "silcd" which would Provide "silc-server".

But if we do that, I would rather rename the binary package produced by
"silc-client" to "silc", for the sake of consistency and make it Provide
"silc-client" as well.

Any opinions?

Cheers,
-- 
Jérémy Bobbio                        .''`. 
lunar at debian.org                    : :Ⓐ  :  # apt-get install anarchism
                                    `. `'` 
                                      `-   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-silc-devel/attachments/20070615/e5900bf8/attachment.pgp