Follow-up Comment #29, task #14945 (project administration):
>> it also has the Linux kernel headers dependency >The point is not whether the package uses kernel headers; the point is whether it makes a single executable with the kernel. The kernel modules clearly do. I think the kernel headers is the actually main point, there are many file system format header file in GPL, if they use it directly then the software itself must be GPL. And the following line creates a executable .ko with the kernel, I don't want to dive into whether the Makefile is conditional or not, its code is distributed with the following Makefile, and people usually don't use this method to judge whether it is GPLed: http://svn.savannah.gnu.org/viewvc/rtai/vulcano/base/tasklets/Makefile.kbuild?view=markup : 10 EXTRA_CFLAGS += -I$(rtai_srctree)/base/include \ 11 -I$(src)/../include \ 12 -I$(src)/../.. \ 13 -D__IN_RTAI__ 14 15 obj-m += $(rtai_target).o 16 17 rtai_tasklets-objs := $(rtai_objs) 18 rtai_signal-objs := $(rtai_objs) In addition, principlly .ko may not be linked into Linux kernel, it could be linked into some Linux Emulator(it could be completely refactor into GPLv2+), or some dumb kernel. This topic is somewhat meaningless, what I say is: 1) The EROFS file system can be licensed as "License: GNU General Public License v2 or later", not GPL-v2 only; 2) Considering effectively, there are projects (the whole or parts of these projects) are GPL-v2 only effectively. If there exist some problems, please point out. Thanks, Gao Xiang _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/task/?14945> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
