On 04/05/2011 05:50 PM, Bruno Haible wrote: > Eric Blake wrote: >> I don't see pipe2 as adding much beyond pipe-posix, cloexec, or >> nonblocking, all of which are LGPLv2+, and libvirt would really like to >> start using atomic fd flag creation routines like pipe2() to avoid data >> races on new enough Linux (the race is still present on other OSs, but >> the code is simpler to write when you use pipe2). >> >> Any objections to relaxing binary-io and pipe2 to LGPLv2+? > > Fine with me. The code in lib/pipe2.c is not trivial, but is library code > similar to glibc's code.
You relaxed pipe2 but not binary-io. Since the former requires the latter, this introduces a licensing conflict. And since the latter only includes a single .h file that just wraps system functions, and given your above agreement to my broader question, I've gone ahead and pushed the obvious followup: 2011-04-06 Eric Blake <[email protected]> binary-io: relicense under LGPLv2+ * modules/binary-io (License): Relax to LGPLv2+. Requested for libvirt, and required by pipe2. -- Eric Blake [email protected] +1-801-349-2682 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
