[zeromq-dev] Debian packaging licensing (was Re: Debian packaging fails (Debian/Lenny, Ubuntu 9.10))

Martin Lucina mato at kotelna.sk
Sat Apr 10 13:18:05 CEST 2010


Hi!

avbidder at fortytwo.ch said:
>
> [snip]
> 
> > Note that I am no licensing expert, I'm just trying to follow the "MIT
> > license for contributions" policy as described by iMatix in the Licensing
> > FAQ and also here:
> > 
> > http://www.zeromq.org/blog:why-the-mit-license-for-contributions
> 
> Ah, of course, should have guessd :-)
> 
> Ok. as per this article:
> 
> +++
> I, Adrian von Bidder, Switzerland, license my work on the Debian packaging of 
> the zeromq library to iMatrix under the MIT/X11 licsense.
> +++

Thanks, acknowledged, I'll take "iMatrix" to mean "iMatix" :-)

> This allows me to avoid dragging yet another license into the mix in the 
> Debian package, and still allows iMatrix to handle the debian/ directory the 
> same as the rest of the code.  (I also modified debian/copyright to say the 
> packaging is LGPL instead of GPL, so we truly have the same license as 
> zeromq.)

Yes, that's the idea, thank you very much. I'm also against any
proliferation of random licenses in the code.

> Obviously Peter needs to either approve or acknowledge that I modified the 
> packaging sufficiently for him to hold no copyright.

I have here an email from Peter which Martin Sustrik forwarded to me (body
attached) which will do for now. Peter, if you can reply with a similar
text as Adrian above that will settle the matter.

> So, here we go...  (Note that this is a few commits after the version that's 
> currently in Debian.  Nothing significant, though.)

OK, am going to apply this right now.

> What would be cool is if somebody wrote a patch that 
>  -> detect that debian/rules is being run not from an extracted tarball but 
> from git, so run autogen.sh before comnfigure.
> 
>  -> ... and optionally tweak the version of the package to include the git 
> commit or something like that.

Yes, I'd like to do this. One thing I'm not sure about is what is the best
practice for the version number from the package in git? Say right now we
have 2.0.7 (not yet released) in git, so the version would be:

zeromq-2.0.7-0~git-1d28dc ?
zeromq-2.0.7-0~git-20100410 ?

Something else ? I'm not sure what the correct format is here. If you can
give any hints that'd be great.

Cheers,

-mato




More information about the zeromq-dev mailing list