[zeromq-dev] RPM packaging for 0MQ

Mikko Koppanen mkoppanen at php.net
Wed May 19 10:42:52 CEST 2010

On Wed, May 19, 2010 at 12:48 AM, David Robinson <zxvdr.au at gmail.com> wrote:
> Couple of things...
> 1) debugging symbols go in a -debuginfo subpackage

As far as I understand -debuginfo is built automatically during the
build process.

> 2) iirc you don't usually specify gcc, make etc as BuildRequires
> because any decent build system will automatically include them since
> practically everything needs them (you'll notice that most packages
> don't specify them even thou they're build by them).

It's a habit I learned on an environment dealing with a lot of
different build machines. Can change easily.

> 3) libraries should probably be split out into a (-lib) subpackage
> (and have the main package require it), that way other packages can
> just require the -lib package if they don't need the binaries.

iirc I modelled the packages after 'curl' packages found in CentOS.
Curl provides two package 'curl' and 'curl-devel' where most of the
libraries and binaries are in 'curl' and development related
functionality in 'curl-devel'. I change that if needed.

> 4) I recommend sending the spec file to the distros to review. Someone
> has already started packaging for Fedora [1] but the process stalled.
> Perhaps you could pick up where they left off (or if you're not
> interested in this I'll try and get the ball rolling again)? Once the
> package is in Fedora you could potentially get it in EPEL too. The
> package review process is rather thorough and the reviewers will be
> able to spot most mistakes.

I've no idea how to collaborate with different distributions. I think
someone mailed me about submitting to Fedora earlier but haven't had
really any time look into this lately.

Mikko Koppanen

More information about the zeromq-dev mailing list