Re: distributing source
Frank Louwers <[email protected]> Sat, 4 Jan 2003 23:03:37 +0100
| Newsgroups | gmane.mail.qmail.dist |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Jan 04, 2003 at 09:43:07PM +0000, [email protected] wrote: > Yury Bokhoncovich writes: > >Though it's OK freely to distribute your patches. I.e. SRPMs and FreeBSD > >ports are OK, RPMs and packages are not. > > This is not entirely true. RPMs and packages are allowed as long as they > produce exactly the same setup as would be achieved by downloading, > compiling and installing the pristine sources: > > "You are permitted to distribute a precompiled var-qmail package if (1) > installing the package produces exactly the same /var/qmail hierarchy as a > user would obtain by downloading, compiling, and installing > qmail-1.03.tar.gz, fastforward-0.51.tar.gz, and dot-forward-0.71.tar.gz; (2) > > the package behaves correctly, i.e., the same way as normal > qmail+fastforward+dot-forward installations on all other systems; and (3) > the package's creator warrants that he has made a good-faith attempt to > ensure that the package behaves correctly." > I have a related question about that. I maintain a few servers, both ours, and at a clients site, some of which are ours, some belong to our clients. We made a few debian packages (basicly from the "official" debian qmail source), with a few modifications in (we use messagewall as a virus/spam blocker, we use vmailmgr for the pops, ...). Theoreticly, when I build that package, login to a client's machine and install that package, I am 'distributing', so I am in violation of the license. Is this correct? What should I do in such a case? Rebuild the package on each machine? Make a "compliant" package and install that first, then make another package that prepares it for messagewall, vmailmgr, ...? Please advise... Kind Regards, Frank Louwers -- Openminds bvba www.openminds.be Tweebruggenstraat 16 - 9000 Gent - Belgium