[Pkg-silc-devel] Next steps!
Jérémy Bobbio
lunar at debian.org
Tue May 22 14:07:08 UTC 2007
Hi!
Here's a roadmap proposal for the freshly created Debian SILC team.
Comments are happily welcome!
1. Alioth
---------
The Alioth project has been created and is now ready to be used. :)
I have currently added micah, schultmc and rekt-guest to the team.
I have subscribed all of you to the pkg-silc-devel mailling-list, and
logically, we should use this email in the maintainer field on the next
package uploads.
Another mailling-list, pkg-silc-commits [1] has been created which
should receive SVN commit notifications. I strongely suggest that we
all subscribe to it.
[1] http://lists.alioth.debian.org/mailman/listinfo/pkg-silc-commits
The subversion repository still need to be created and configured.
will try to do it during the evening (but someone else can do it before
me!)
2. Getting packages into SVN
----------------------------
Once we'll have the subversion repository ready, I suggest that we
import (using svn-import in svn-buildpackage) all the packages mentioned
in my initial email.
Which are:
* from the main archive: silc-toolkit, silky
* from dkg's repository: silc-client, silc-server
I would also like to see if the upstream for Kopete SILC plugin [1], who
currently provide their own Debian package [2], would let us go one with
their packaging. If they agree, we definetely should import their
current package as well.
[1] http://brokenpipe.de/SILC/
[2] http://www.brokenpipe.de/debian/pool/main/k/
3a. Update silc-toolkit and silc-client
---------------------------------------
silc-toolkit and silc-client are outdated ATM. Last upstream versions
are:
* SILC Toolkit 1.1 beta 5
* SILC Client 1.1 beta 3
3b. Fix silky
-------------
silky is currently quite broken.
My current intution is that it might be related to a mixup between
"guchar" and "gchar" usage all through the code.
Sounds like something doable but quite tedious to do.
Upstream development seems unfortunately completely stopped. A
responsible move in this regard would be to remove the package from the
archive. But I don't advocate for such solution as: silky would be
usuable without the segfaults and we don't have any other alternatives
currently.
3c. Get silc-toolkit in perfect shape if it's not already
---------------------------------------------------------
silc-toolkit will be the first shared library that I'll be responsible
for. I started reading dancer's "Debian Library Packaging guide" [1]
with this in mind.
I didn't took the time (yet) to compare the current silc-toolkit package
with the best practices mentioned in this guide, but I would really like
to convince pidgin maintainers to enable the SILC plugin.
So we should be able convince them and whatever is needed to do so.
[1] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
3d. Have irssi-plugin-silc ready
--------------------------------
SILC Client 1.1 beta 3 finally contain the ability to build the irssi
plugin without the previous complexity that it was before.
I would enjoy to see silc-client producing a binary package
"irssi-plugin-silc" quite soon using solely upstream tarball.
But it will not be completely correct regarding the Debian policy as we
should normally be using the irssi-dev package as a dependancy instead
of the source copy present in upstream tarball.
My investigation showed that irssi-dev is currently missing the ability
to produce Perl modules needed for a complete out of tree build of the
SILC plugin.
This will be quite some work to change both irssi-dev and the upstream
source code to achieve Debian policy compliance. So I suggest that we
upload a initial version first, immediately adding an "important" bug
mentionning the code duplication issue.
What do you think? :)
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/20070522/584f3f3a/attachment.pgp
More information about the Pkg-silc-devel
mailing list