[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: relax license of cloexec, fcntl

From: Bruno Haible
Subject: Re: relax license of cloexec, fcntl
Date: Sat, 11 Dec 2010 04:04:35 +0100
User-agent: KMail/1.9.9

Hi Eric,

> cloexec (currently LGPLv3+),  fcntl (currently LGPLv3+).
> Are there any objections to relaxing the license?

Fine with me. lib/fcntl.c contains some originally GPLed code from me
(the DuplicateHandle stuff: originally in lib/w32spawn.h under GPL,
moved to lib/cloexec.c on 2009-12-05, became LGPLv3+ on 2009-12-10,
moved to lib/fcntl.c on 2009-12-16), but that is not worth considering
as very valuable.

Eric Blake wrote:
> I will want to make open (LGPLv2+) depend on cloexec

We carefully avoided to have such a dependency. I guess that at least
some people would consider it "creepy dependencies": The 'open' module fixes
a number of problems that people usually want to avoid. But 'cloexec'
is useful only in programs that spawn subprocesses. Programs that simply
manipulate files without having subprocesses will not need this. How
about having two modules 'open' and 'open-cloexec' (or maybe 'open-posix')?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]