ACL package --- GPL or LGPL?
"Stephen C. Tweedie" <[email protected]> 16 Nov 2004 13:15:24 +0000
| Newsgroups | gmane.linux.file-systems.acl.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, The ACL package seems to be nearly entirely LGPL. Almost all the .c and .h files are, and the only license in doc/* is LGPL. Yet the Makefiles are GPLed, and the license in the canned rpm and debian build files mention GPL or both. And oddly, even part of libacl is GPLed (and I'd have thought libacl was the one most likely to need to be LGPL.) acl/libacl/perm_copy_fd.c acl/libacl/perm_copy_file.c are both GPLed; the utilities are LGPLed except for chacl(). Is this inconsistency deliberate? I've just had a bug report against the Red Hat rpms which complains that our rpm lists the package as GPL, where it's really LGPL. But unless it's _all_ LGPL, we can't really change the rpm license tag. Similarly, libattr is a combination, with GPLed files: attr/libattr/attr_copy_check.c attr/libattr/attr_copy_file.c attr/libattr/attr_copy_fd.c contaminating an otherwise-LGPLable library. Cheers, Stephen _______________________________________________ acl-devel mailing list [email protected] http://acl.bestbits.at/mailman/listinfo/acl-devel