Qmail
[Top] [All Lists]

Re: qmail license question

To: qmail@list.cr.yp.to
Subject: Re: qmail license question
From: Jeremy Kitchen <kitchen@scriptkitchen.com>
Date: Wed, 07 Mar 2007 13:36:58 -0800
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-qmail@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list qmail@list.cr.yp.to
In-reply-to: <924f29280703071315o25bcb3b1vf1054c19dbcad37a@mail.gmail.com>
Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
References: <924f29280703071315o25bcb3b1vf1054c19dbcad37a@mail.gmail.com>
User-agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
Jason Frisvold wrote:
> As I understand it, the licensing for qmail basically says that you
> can distribute the source code, distribute patches to the source code,
> but not distribute any binary copies.  Is that accurate?

Nor a modified source tarball.  netqmail does not distributed a modified
source tarball.. it includes the 'official' source tarball inside its own.

And, you actually *can* distribute pre-built binaries, so long as
they're 'var-qmail' compatible.

See: http://cr.yp.to/qmail/dist.html

> Based on that, would I be allowed to distribute an SRPM with the
> original source and all my patches?  (Please, no flamewars about my
> choice of packager)  Or does that violate the licensing?

As far as I know, that's fine.. there are several packages that do this
already.

> I believe there's another package that distributes qmail in a binary
> form, though the name escapes me at the moment.  However, I think
> that's a known issue as that's definitely not allowed.  I've see some
> brief discussion of that here.

The evil P word.

-Jeremy

Attachment: signature.asc
Description: OpenPGP digital signature

<Prev in Thread] Current Thread [Next in Thread>