[zeromq-dev] Debian packaging: current status & where to go from there

[Adrian von Bidder]

Heyho!

After the various discussions (thanks a lot for your input, all!):

 * Debian package currently takes place in my Mercurial tree at 
<https://fortytwo.ch/hg/pkg-zeromq>
 * The package is built from the 2.0beta2 tarball.  I plan to stick to 
tarball releases whenever possible.
 * The package, only C/C++ bindings for now, has been uploaded and will new 
be reviewed by ftpmasters in due time.
 * In the mean time, you can look at http://fortytwo.ch/debian/zeromq/

Since I started packaging without noticing the existing work from Peter 
(which was not yet included in the beta2 tarball), it doesn't make sense to 
try to merge (in the vcs sense) the packaging.  I took most of the 
description from Peter because it is quite a bit better than what I had, and 
his work still helped me getting my packaging into shape.

Now, where to go from here:

 * ship example code and perf stuff with the -dev package as sugggested.

 * enable language bindings, probably one by one.
   (It is quite important that the linking issues are fixed; not only is the 
python library not linked with -lpython2.5 as I mentioned previously, but at 
least the java JNI library ends up being linked with -lruby1.8, which 
probably is not what is intended.  I'm absolutely not an autoconf/make guru, 
though.)

 * Of course, if you're faster with splitting of language bindings into 
their own packages than I am with packaging them, it gets easier for me.  
Right now, I don't plan to package seperately released languages.

 * As discussed it makes sense to integrate the debian/ directory into the 
upstream sources (I can still ship a modified package after all.)  As long 
as I don't have any language bindings enabled (Peter's work had working 
packages at least for CL), I guess we should postpone that (but this is 
ultimately not my decision; for me, it's ok for you to grab "my" debian/ 
directory as soon as you want.)

 * not directly dependent, but it would be convenient ... yes, I plan to 
learn git at some time.  Shouldn't be that hard, coming from hg.  Just not 
in the next few days, so expect the hg based tree to stick around for a 
while.  If you decide to ship my packaging, I will (try to remember to) send 
my changes for inclusion, too.

Ok, so long.

cheers
-- vbi

P.S.: listmasters: is this list half-broken?  I seem to get only part of the 
mail, especially I think I didn't get some of the messages from our 
packaging discussions through the list; I did only get them as cc:s.  I 
don't remember installing duplication-removal software at my end.


-- 
Remember that DEFAULT_MOD is Mod1, which on normal Linux (and most UNIX)
systems is the Alt key. The Alt key is also known as the Meta key, but
of course in Emacs you can access Meta with the Esc key, (while in
Solaris, the Meta key looks like a diamond and the Alt key is just Alt).
If you could follow the last sentence, you have my sympathies!
        -- Teodor Zlatanov about ion
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 389 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20100126/54c41ca7/attachment.sig>