* [Xenomai] License Issues
@ 2015-06-17 16:25 Leopold Palomo-Avellaneda
2015-06-17 16:48 ` Lennart Sorensen
2015-06-17 17:25 ` Gilles Chanteperdrix
0 siblings, 2 replies; 14+ messages in thread
From: Leopold Palomo-Avellaneda @ 2015-06-17 16:25 UTC (permalink / raw)
To: xenomai
Hi,
using a debian tool to check the license of the package I have found that his
files:
examples/Makefile
examples/common/Makefile
examples/native/Makefile
examples/native/rtprint.c
examples/native/sigdebug.c
examples/native/trivial-periodic.c
examples/posix/Makefile
examples/posix/README
examples/rtdm/driver-api/Makefile
examples/rtdm/profiles/can/Makefile
examples/rtdm/profiles/ipc/Makefile
examples/rtdm/profiles/ipc/bufp-label.c
examples/rtdm/profiles/ipc/bufp-readwrite.c
examples/rtdm/profiles/ipc/iddp-label.c
examples/rtdm/profiles/ipc/iddp-sendrecv.c
examples/rtdm/profiles/ipc/xddp-echo.c
examples/rtdm/profiles/ipc/xddp-label.c
examples/rtdm/profiles/ipc/xddp-stream.c
examples/rtdm/profiles/serial/Makefile
include/Makefile.am
include/analogy/Makefile.am
include/asm-arm/Makefile.am
include/asm-arm/bits/Makefile.am
include/asm-blackfin/Makefile.am
include/asm-blackfin/bits/Makefile.am
include/asm-blackfin/bits/bind.h
include/asm-blackfin/fptest.h
include/asm-generic/Makefile.am
include/asm-generic/bits/Makefile.am
include/asm-generic/pci_ids.h
include/asm-nios2/Makefile.am
include/asm-nios2/bits/Makefile.am
include/asm-nios2/bits/bind.h
include/asm-nios2/fptest.h
include/asm-powerpc/Makefile.am
include/asm-powerpc/bits/Makefile.am
include/asm-powerpc/bits/bind.h
include/asm-powerpc/fptest.h
include/asm-sh/Makefile.am
include/asm-sh/bits/Makefile.am
include/asm-sh/bits/bind.h
include/asm-sh/fptest.h
include/asm-sim/Makefile.am
include/asm-sim/bits/Makefile.am
include/asm-x86/Makefile.am
include/asm-x86/arith.h
include/asm-x86/bits/Makefile.am
include/asm-x86/bits/pod.h
include/asm-x86/features.h
include/asm-x86/switch.h
include/asm-x86/system.h
include/asm-x86/wrappers.h
include/compat/asm-i386/io_ports.h
include/compat/linux/calc64.h
include/native/Makefile.am
include/nucleus/Makefile.am
include/nucleus/seqlock.h
include/posix/Makefile.am
include/posix/sys/Makefile.am
include/psos+/Makefile.am
include/psos+/long_names.h
include/rtdm/Makefile.am
include/testing/sigtest_syscall.h
include/uitron/Makefile.am
include/vrtx/Makefile.am
include/vrtx/vrtx.h
include/vxworks/Makefile.am
include/vxworks/vxworks.h
ksrc/Config.in
ksrc/Makefile
ksrc/arch/Makefile
ksrc/arch/arm/Kconfig
ksrc/arch/arm/Makefile
ksrc/arch/arm/patches/README
ksrc/arch/arm/patches/beaglebone/ipipe-core-3.8.13-beaglebone-
post.patch
ksrc/arch/arm/patches/beaglebone/ipipe-core-3.8.13-beaglebone-
pre.patch
ksrc/arch/arm/patches/ipipe-core-3.10.32-arm-5.patch
ksrc/arch/arm/patches/ipipe-core-3.8.13-arm-4.patch
ksrc/arch/arm/patches/raspberry/ipipe-core-3.8.13-raspberry-post-2.patch
ksrc/arch/arm/patches/raspberry/ipipe-core-3.8.13-raspberry-pre-2.patch
ksrc/arch/arm/patches/zynq/ipipe-core-3.5.7-zynq-post.patch
ksrc/arch/arm/patches/zynq/ipipe-core-3.5.7-zynq-pre.patch
ksrc/arch/arm/patches/zynq/ipipe-core-3.8-zynq-post.patch
ksrc/arch/arm/patches/zynq/ipipe-core-3.8-zynq-pre.patch
ksrc/arch/blackfin/Config.in
ksrc/arch/blackfin/Kconfig
ksrc/arch/blackfin/Makefile
ksrc/arch/blackfin/patches/README
ksrc/arch/blackfin/patches/ipipe-core-3.10.32-blackfin-3.patch
ksrc/arch/blackfin/patches/ipipe-core-3.14.17-blackfin-4.patch
ksrc/arch/blackfin/patches/ipipe-core-3.8.13-blackfin-2.patch
ksrc/arch/generic/Makefile
ksrc/arch/generic/compat.c
ksrc/arch/nios2/Config.in
ksrc/arch/nios2/Kconfig
ksrc/arch/nios2/Makefile
ksrc/arch/nios2/patches/README
ksrc/arch/powerpc/Config.in
ksrc/arch/powerpc/Kconfig
ksrc/arch/powerpc/Makefile
ksrc/arch/powerpc/patches/README
ksrc/arch/powerpc/patches/ipipe-core-3.10.32-powerpc-4.patch
ksrc/arch/powerpc/patches/ipipe-core-3.14.17-powerpc-4.patch
ksrc/arch/powerpc/patches/ipipe-core-3.8.13-powerpc-2.patch
ksrc/arch/sh/Kconfig
ksrc/arch/sh/Makefile
ksrc/arch/sh/patches/README
ksrc/arch/x86/Config.in
ksrc/arch/x86/Kconfig
ksrc/arch/x86/Makefile
ksrc/arch/x86/patches/README
ksrc/arch/x86/patches/ipipe-core-3.10.32-x86-4.patch
ksrc/arch/x86/patches/ipipe-core-3.14.17-x86-4.patch
ksrc/arch/x86/patches/ipipe-core-3.8.13-x86-4.patch
ksrc/drivers/Config.in
ksrc/drivers/Kconfig
ksrc/drivers/Makefile
ksrc/drivers/analogy/Config.in
ksrc/drivers/analogy/Kconfig
ksrc/drivers/analogy/Makefile
ksrc/drivers/analogy/intel/Config.in
ksrc/drivers/analogy/intel/Kconfig
ksrc/drivers/analogy/intel/Makefile
ksrc/drivers/analogy/national_instruments/Config.in
ksrc/drivers/analogy/national_instruments/Kconfig
ksrc/drivers/analogy/national_instruments/Makefile
ksrc/drivers/analogy/sensoray/Config.in
ksrc/drivers/analogy/sensoray/Kconfig
ksrc/drivers/analogy/sensoray/Makefile
ksrc/drivers/analogy/testing/Config.in
ksrc/drivers/analogy/testing/Kconfig
ksrc/drivers/analogy/testing/Makefile
ksrc/drivers/analogy/testing/fake.c
ksrc/drivers/can/CREDITS
ksrc/drivers/can/Config.in
ksrc/drivers/can/Kconfig
ksrc/drivers/can/Makefile
ksrc/drivers/can/README
ksrc/drivers/can/mscan/Config.in
ksrc/drivers/can/mscan/Kconfig
ksrc/drivers/can/mscan/Makefile
ksrc/drivers/can/mscan/rtcan_mscan.c
ksrc/drivers/can/mscan/rtcan_mscan_mpc52xx.c
ksrc/drivers/can/rtcan_internal.h
ksrc/drivers/can/rtcan_module.c
ksrc/drivers/can/sja1000/Config.in
ksrc/drivers/can/sja1000/Kconfig
ksrc/drivers/can/sja1000/Makefile
ksrc/drivers/can/sja1000/rtcan_esd_pci.c
ksrc/drivers/can/sja1000/rtcan_peak_dng.c
ksrc/drivers/can/sja1000/rtcan_peak_pci.c
ksrc/drivers/can/sja1000/rtcan_plx_pci.c
ksrc/drivers/ipc/Config.in
ksrc/drivers/ipc/Kconfig
ksrc/drivers/ipc/Makefile
ksrc/drivers/serial/Config.in
ksrc/drivers/serial/Kconfig
ksrc/drivers/serial/Makefile
ksrc/drivers/testing/Config.in
ksrc/drivers/testing/Kconfig
ksrc/drivers/testing/Makefile
ksrc/drivers/testing/sigtest_module.c
ksrc/nucleus/Config.in
ksrc/nucleus/Kconfig
ksrc/nucleus/Makefile
ksrc/nucleus/udev/rtheap.rules
ksrc/nucleus/udev/rtpipe.rules
ksrc/skins/Config.in
ksrc/skins/Kconfig
ksrc/skins/Makefile
ksrc/skins/native/API.CHANGES
ksrc/skins/native/Config.in
ksrc/skins/native/Kconfig
ksrc/skins/native/Makefile
ksrc/skins/native/demos/Makefile
ksrc/skins/native/demos/latency.c
ksrc/skins/native/demos/satch.c
ksrc/skins/native/snippets/bound_task.c
ksrc/skins/native/snippets/cond_var.c
ksrc/skins/native/snippets/event_flags.c
ksrc/skins/native/snippets/kernel_task.c
ksrc/skins/native/snippets/local_heap.c
ksrc/skins/native/snippets/msg_queue.c
ksrc/skins/native/snippets/mutex.c
ksrc/skins/native/snippets/pipe.c
ksrc/skins/native/snippets/semaphore.c
ksrc/skins/native/snippets/shared_mem.c
ksrc/skins/native/snippets/sigxcpu.c
ksrc/skins/native/snippets/user_alarm.c
ksrc/skins/native/snippets/user_irq.c
ksrc/skins/native/snippets/user_task.c
ksrc/skins/posix/Config.in
ksrc/skins/posix/Kconfig
ksrc/skins/posix/Makefile
ksrc/skins/posix/apc.h
ksrc/skins/posix/cancel.c
ksrc/skins/posix/cancel.h
ksrc/skins/posix/cb_lock.h
ksrc/skins/posix/clock.c
ksrc/skins/posix/cond.c
ksrc/skins/posix/cond.h
ksrc/skins/posix/cond_attr.c
ksrc/skins/posix/demos/Kbuild
ksrc/skins/posix/demos/Makefile
ksrc/skins/posix/demos/accuracy.c
ksrc/skins/posix/internal.h
ksrc/skins/posix/module.c
ksrc/skins/posix/mq.c
ksrc/skins/posix/mq.h
ksrc/skins/posix/mutex.c
ksrc/skins/posix/mutex.h
ksrc/skins/posix/mutex_attr.c
ksrc/skins/posix/once.c
ksrc/skins/posix/registry.c
ksrc/skins/posix/registry.h
ksrc/skins/posix/sched.c
ksrc/skins/posix/sem.c
ksrc/skins/posix/sem.h
ksrc/skins/posix/shm.h
ksrc/skins/posix/sig.h
ksrc/skins/posix/signal.c
ksrc/skins/posix/thread.c
ksrc/skins/posix/thread.h
ksrc/skins/posix/thread_attr.c
ksrc/skins/posix/tsd.c
ksrc/skins/posix/tsd.h
ksrc/skins/psos+/API.CHANGES
ksrc/skins/psos+/Config.in
ksrc/skins/psos+/Kconfig
ksrc/skins/psos+/Makefile
ksrc/skins/psos+/demos/Makefile
ksrc/skins/rtdm/API.CHANGES
ksrc/skins/rtdm/Config.in
ksrc/skins/rtdm/Kconfig
ksrc/skins/rtdm/Makefile
ksrc/skins/uitron/Config.in
ksrc/skins/uitron/Kconfig
ksrc/skins/uitron/Makefile
ksrc/skins/vrtx/Config.in
ksrc/skins/vrtx/Kconfig
ksrc/skins/vrtx/Makefile
ksrc/skins/vrtx/defs.h
ksrc/skins/vrtx/event.c
ksrc/skins/vrtx/event.h
ksrc/skins/vrtx/heap.c
ksrc/skins/vrtx/heap.h
ksrc/skins/vrtx/mb.c
ksrc/skins/vrtx/mb.h
ksrc/skins/vrtx/module.c
ksrc/skins/vrtx/mx.c
ksrc/skins/vrtx/mx.h
ksrc/skins/vrtx/pt.c
ksrc/skins/vrtx/pt.h
ksrc/skins/vrtx/queue.c
ksrc/skins/vrtx/queue.h
ksrc/skins/vrtx/sem.c
ksrc/skins/vrtx/sem.h
ksrc/skins/vrtx/task.c
ksrc/skins/vrtx/task.h
ksrc/skins/vrtx/time.c
ksrc/skins/vxworks/Config.in
ksrc/skins/vxworks/Kconfig
ksrc/skins/vxworks/Makefile
ksrc/skins/vxworks/defs.h
ksrc/skins/vxworks/demos/Makefile
ksrc/skins/vxworks/errnoLib.c
ksrc/skins/vxworks/intLib.c
ksrc/skins/vxworks/kernelLib.c
ksrc/skins/vxworks/module.c
ksrc/skins/vxworks/msgQLib.c
ksrc/skins/vxworks/semLib.c
ksrc/skins/vxworks/sysLib.c
ksrc/skins/vxworks/taskHookLib.c
ksrc/skins/vxworks/taskInfo.c
ksrc/skins/vxworks/taskLib.c
ksrc/skins/vxworks/tickLib.c
ksrc/skins/vxworks/wdLib.c
scripts/Kconfig.frag
scripts/Makefile.am
scripts/Modules.frag
scripts/bootstrap
scripts/defconfig.frag
scripts/help_from_kconfig.pl
scripts/histo.gp
scripts/prepare-kernel.sh
scripts/wrap-link.sh
scripts/xeno-config.in
scripts/xeno.in
src/Makefile.am
src/drvlib/Makefile.am
src/drvlib/analogy/Makefile.am
src/include/Makefile.am
src/include/xeno_config.h.in
src/skins/Makefile.am
src/skins/common/Makefile.am
src/skins/native/Makefile.am
src/skins/native/libxenomai_native.pc.in
src/skins/native/wrappers.h
src/skins/posix/Makefile.am
src/skins/posix/libxenomai_posix.pc.in
src/skins/posix/posix.wrappers
src/skins/psos+/Makefile.am
src/skins/psos+/libxenomai_psos+.pc.in
src/skins/rtdm/Makefile.am
src/skins/rtdm/libxenomai_rtdm.pc.in
src/skins/uitron/Makefile.am
src/skins/uitron/libxenomai_uitron.pc.in
src/skins/vrtx/Makefile.am
src/skins/vrtx/libxenomai_vrtx.pc.in
src/skins/vrtx/wrappers.h
src/skins/vxworks/Makefile.am
src/skins/vxworks/libxenomai_vxworks.pc.in
src/skins/vxworks/wrappers.h
src/testsuite/Makefile.am
src/testsuite/clocktest/Makefile.am
src/testsuite/cyclic/Makefile.am
src/testsuite/irqbench/Makefile.am
src/testsuite/klatency/Makefile.am
src/testsuite/latency/Makefile.am
src/testsuite/latency/latency.c
src/testsuite/regression/Makefile.am
src/testsuite/regression/native+posix/Makefile.am
src/testsuite/regression/native/Makefile.am
src/testsuite/regression/posix/Makefile.am
src/testsuite/regression/posix/xddp_test.c
src/testsuite/regression/xeno-regression-test.in
src/testsuite/switchtest/Makefile.am
src/testsuite/unit/Makefile.am
src/testsuite/unit/check-vdso.c
src/testsuite/unit/wakeup-time.c
src/testsuite/xeno-test/Makefile.am
src/testsuite/xeno-test/dohell
src/testsuite/xeno-test/xeno-test-run-wrapper
src/testsuite/xeno-test/xeno-test.in
src/utils/Makefile.am
src/utils/analogy/Makefile.am
src/utils/analogy/wf_facilities.c
src/utils/analogy/wf_facilities.h
src/utils/can/Makefile.am
src/utils/can/README
src/utils/ps/Makefile.am
src/utils/ps/rtps.c
Have no license defined or i have not found it. Please, could you put some
lines to clarify that?
Best regards,
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150617/0a9720b1/attachment.sig>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-17 16:25 [Xenomai] License Issues Leopold Palomo-Avellaneda
@ 2015-06-17 16:48 ` Lennart Sorensen
2015-06-17 21:36 ` Leopold Palomo-Avellaneda
2015-06-17 17:25 ` Gilles Chanteperdrix
1 sibling, 1 reply; 14+ messages in thread
From: Lennart Sorensen @ 2015-06-17 16:48 UTC (permalink / raw)
To: Leopold Palomo-Avellaneda; +Cc: xenomai
On Wed, Jun 17, 2015 at 06:25:05PM +0200, Leopold Palomo-Avellaneda wrote:
> Hi,
>
> using a debian tool to check the license of the package I have found that his
> files:
Well here is my guess based on reading what is there. And besides who
says all files have to mention the license themselves? The directory
could have that info or the entire project.
> examples/Makefile
> examples/common/Makefile
> examples/native/Makefile
> examples/native/rtprint.c
> examples/native/sigdebug.c
> examples/native/trivial-periodic.c
> examples/posix/Makefile
> examples/posix/README
> examples/rtdm/driver-api/Makefile
> examples/rtdm/profiles/can/Makefile
> examples/rtdm/profiles/ipc/Makefile
> examples/rtdm/profiles/ipc/bufp-label.c
> examples/rtdm/profiles/ipc/bufp-readwrite.c
> examples/rtdm/profiles/ipc/iddp-label.c
> examples/rtdm/profiles/ipc/iddp-sendrecv.c
> examples/rtdm/profiles/ipc/xddp-echo.c
> examples/rtdm/profiles/ipc/xddp-label.c
> examples/rtdm/profiles/ipc/xddp-stream.c
> examples/rtdm/profiles/serial/Makefile
No idea.
> include/Makefile.am
> include/analogy/Makefile.am
> include/asm-arm/Makefile.am
> include/asm-arm/bits/Makefile.am
> include/asm-blackfin/Makefile.am
> include/asm-blackfin/bits/Makefile.am
> include/asm-blackfin/bits/bind.h
> include/asm-blackfin/fptest.h
> include/asm-generic/Makefile.am
> include/asm-generic/bits/Makefile.am
> include/asm-generic/pci_ids.h
> include/asm-nios2/Makefile.am
> include/asm-nios2/bits/Makefile.am
> include/asm-nios2/bits/bind.h
> include/asm-nios2/fptest.h
> include/asm-powerpc/Makefile.am
> include/asm-powerpc/bits/Makefile.am
> include/asm-powerpc/bits/bind.h
> include/asm-powerpc/fptest.h
> include/asm-sh/Makefile.am
> include/asm-sh/bits/Makefile.am
> include/asm-sh/bits/bind.h
> include/asm-sh/fptest.h
> include/asm-sim/Makefile.am
> include/asm-sim/bits/Makefile.am
> include/asm-x86/Makefile.am
> include/asm-x86/arith.h
> include/asm-x86/bits/Makefile.am
> include/asm-x86/bits/pod.h
> include/asm-x86/features.h
> include/asm-x86/switch.h
> include/asm-x86/system.h
> include/asm-x86/wrappers.h
> include/compat/asm-i386/io_ports.h
> include/compat/linux/calc64.h
> include/native/Makefile.am
> include/nucleus/Makefile.am
> include/nucleus/seqlock.h
> include/posix/Makefile.am
> include/posix/sys/Makefile.am
> include/psos+/Makefile.am
> include/psos+/long_names.h
> include/rtdm/Makefile.am
> include/testing/sigtest_syscall.h
> include/uitron/Makefile.am
> include/vrtx/Makefile.am
> include/vrtx/vrtx.h
> include/vxworks/Makefile.am
> include/vxworks/vxworks.h
Seems to be covered by include/COPYING
> ksrc/Config.in
> ksrc/Makefile
> ksrc/arch/Makefile
> ksrc/arch/arm/Kconfig
> ksrc/arch/arm/Makefile
> ksrc/arch/arm/patches/README
> ksrc/arch/arm/patches/beaglebone/ipipe-core-3.8.13-beaglebone-post.patch
> ksrc/arch/arm/patches/beaglebone/ipipe-core-3.8.13-beaglebone-pre.patch
> ksrc/arch/arm/patches/ipipe-core-3.10.32-arm-5.patch
> ksrc/arch/arm/patches/ipipe-core-3.8.13-arm-4.patch
> ksrc/arch/arm/patches/raspberry/ipipe-core-3.8.13-raspberry-post-2.patch
> ksrc/arch/arm/patches/raspberry/ipipe-core-3.8.13-raspberry-pre-2.patch
> ksrc/arch/arm/patches/zynq/ipipe-core-3.5.7-zynq-post.patch
> ksrc/arch/arm/patches/zynq/ipipe-core-3.5.7-zynq-pre.patch
> ksrc/arch/arm/patches/zynq/ipipe-core-3.8-zynq-post.patch
> ksrc/arch/arm/patches/zynq/ipipe-core-3.8-zynq-pre.patch
> ksrc/arch/blackfin/Config.in
> ksrc/arch/blackfin/Kconfig
> ksrc/arch/blackfin/Makefile
> ksrc/arch/blackfin/patches/README
> ksrc/arch/blackfin/patches/ipipe-core-3.10.32-blackfin-3.patch
> ksrc/arch/blackfin/patches/ipipe-core-3.14.17-blackfin-4.patch
> ksrc/arch/blackfin/patches/ipipe-core-3.8.13-blackfin-2.patch
> ksrc/arch/generic/Makefile
> ksrc/arch/generic/compat.c
> ksrc/arch/nios2/Config.in
> ksrc/arch/nios2/Kconfig
> ksrc/arch/nios2/Makefile
> ksrc/arch/nios2/patches/README
> ksrc/arch/powerpc/Config.in
> ksrc/arch/powerpc/Kconfig
> ksrc/arch/powerpc/Makefile
> ksrc/arch/powerpc/patches/README
> ksrc/arch/powerpc/patches/ipipe-core-3.10.32-powerpc-4.patch
> ksrc/arch/powerpc/patches/ipipe-core-3.14.17-powerpc-4.patch
> ksrc/arch/powerpc/patches/ipipe-core-3.8.13-powerpc-2.patch
> ksrc/arch/sh/Kconfig
> ksrc/arch/sh/Makefile
> ksrc/arch/sh/patches/README
> ksrc/arch/x86/Config.in
> ksrc/arch/x86/Kconfig
> ksrc/arch/x86/Makefile
> ksrc/arch/x86/patches/README
> ksrc/arch/x86/patches/ipipe-core-3.10.32-x86-4.patch
> ksrc/arch/x86/patches/ipipe-core-3.14.17-x86-4.patch
> ksrc/arch/x86/patches/ipipe-core-3.8.13-x86-4.patch
> ksrc/drivers/Config.in
> ksrc/drivers/Kconfig
> ksrc/drivers/Makefile
> ksrc/drivers/analogy/Config.in
> ksrc/drivers/analogy/Kconfig
> ksrc/drivers/analogy/Makefile
> ksrc/drivers/analogy/intel/Config.in
> ksrc/drivers/analogy/intel/Kconfig
> ksrc/drivers/analogy/intel/Makefile
> ksrc/drivers/analogy/national_instruments/Config.in
> ksrc/drivers/analogy/national_instruments/Kconfig
> ksrc/drivers/analogy/national_instruments/Makefile
> ksrc/drivers/analogy/sensoray/Config.in
> ksrc/drivers/analogy/sensoray/Kconfig
> ksrc/drivers/analogy/sensoray/Makefile
> ksrc/drivers/analogy/testing/Config.in
> ksrc/drivers/analogy/testing/Kconfig
> ksrc/drivers/analogy/testing/Makefile
> ksrc/drivers/analogy/testing/fake.c
> ksrc/drivers/can/CREDITS
> ksrc/drivers/can/Config.in
> ksrc/drivers/can/Kconfig
> ksrc/drivers/can/Makefile
> ksrc/drivers/can/README
> ksrc/drivers/can/mscan/Config.in
> ksrc/drivers/can/mscan/Kconfig
> ksrc/drivers/can/mscan/Makefile
> ksrc/drivers/can/mscan/rtcan_mscan.c
> ksrc/drivers/can/mscan/rtcan_mscan_mpc52xx.c
> ksrc/drivers/can/rtcan_internal.h
> ksrc/drivers/can/rtcan_module.c
> ksrc/drivers/can/sja1000/Config.in
> ksrc/drivers/can/sja1000/Kconfig
> ksrc/drivers/can/sja1000/Makefile
> ksrc/drivers/can/sja1000/rtcan_esd_pci.c
> ksrc/drivers/can/sja1000/rtcan_peak_dng.c
> ksrc/drivers/can/sja1000/rtcan_peak_pci.c
> ksrc/drivers/can/sja1000/rtcan_plx_pci.c
> ksrc/drivers/ipc/Config.in
> ksrc/drivers/ipc/Kconfig
> ksrc/drivers/ipc/Makefile
> ksrc/drivers/serial/Config.in
> ksrc/drivers/serial/Kconfig
> ksrc/drivers/serial/Makefile
> ksrc/drivers/testing/Config.in
> ksrc/drivers/testing/Kconfig
> ksrc/drivers/testing/Makefile
> ksrc/drivers/testing/sigtest_module.c
No idea. Although given it is applied as a patch to a linux kernel,
one would think GPLv2 is the only option it could be under.
> ksrc/nucleus/Config.in
> ksrc/nucleus/Kconfig
> ksrc/nucleus/Makefile
> ksrc/nucleus/udev/rtheap.rules
> ksrc/nucleus/udev/rtpipe.rules
ksrc/nucleus/COPYING
> ksrc/skins/Config.in
> ksrc/skins/Kconfig
> ksrc/skins/Makefile
> ksrc/skins/native/API.CHANGES
> ksrc/skins/native/Config.in
> ksrc/skins/native/Kconfig
> ksrc/skins/native/Makefile
> ksrc/skins/native/demos/Makefile
> ksrc/skins/native/demos/latency.c
> ksrc/skins/native/demos/satch.c
> ksrc/skins/native/snippets/bound_task.c
> ksrc/skins/native/snippets/cond_var.c
> ksrc/skins/native/snippets/event_flags.c
> ksrc/skins/native/snippets/kernel_task.c
> ksrc/skins/native/snippets/local_heap.c
> ksrc/skins/native/snippets/msg_queue.c
> ksrc/skins/native/snippets/mutex.c
> ksrc/skins/native/snippets/pipe.c
> ksrc/skins/native/snippets/semaphore.c
> ksrc/skins/native/snippets/shared_mem.c
> ksrc/skins/native/snippets/sigxcpu.c
> ksrc/skins/native/snippets/user_alarm.c
> ksrc/skins/native/snippets/user_irq.c
> ksrc/skins/native/snippets/user_task.c
ksrc/skins/native/COPYING
> ksrc/skins/posix/Config.in
> ksrc/skins/posix/Kconfig
> ksrc/skins/posix/Makefile
> ksrc/skins/posix/apc.h
> ksrc/skins/posix/cancel.c
> ksrc/skins/posix/cancel.h
> ksrc/skins/posix/cb_lock.h
> ksrc/skins/posix/clock.c
> ksrc/skins/posix/cond.c
> ksrc/skins/posix/cond.h
> ksrc/skins/posix/cond_attr.c
> ksrc/skins/posix/demos/Kbuild
> ksrc/skins/posix/demos/Makefile
> ksrc/skins/posix/demos/accuracy.c
> ksrc/skins/posix/internal.h
> ksrc/skins/posix/module.c
> ksrc/skins/posix/mq.c
> ksrc/skins/posix/mq.h
> ksrc/skins/posix/mutex.c
> ksrc/skins/posix/mutex.h
> ksrc/skins/posix/mutex_attr.c
> ksrc/skins/posix/once.c
> ksrc/skins/posix/registry.c
> ksrc/skins/posix/registry.h
> ksrc/skins/posix/sched.c
> ksrc/skins/posix/sem.c
> ksrc/skins/posix/sem.h
> ksrc/skins/posix/shm.h
> ksrc/skins/posix/sig.h
> ksrc/skins/posix/signal.c
> ksrc/skins/posix/thread.c
> ksrc/skins/posix/thread.h
> ksrc/skins/posix/thread_attr.c
> ksrc/skins/posix/tsd.c
> ksrc/skins/posix/tsd.h
ksrc/skins/posix/COPYING
> ksrc/skins/psos+/API.CHANGES
> ksrc/skins/psos+/Config.in
> ksrc/skins/psos+/Kconfig
> ksrc/skins/psos+/Makefile
> ksrc/skins/psos+/demos/Makefile
ksrc/skins/psos+/COPYING
> ksrc/skins/rtdm/API.CHANGES
> ksrc/skins/rtdm/Config.in
> ksrc/skins/rtdm/Kconfig
> ksrc/skins/rtdm/Makefile
ksrc/skins/rtdm/COPYING
> ksrc/skins/uitron/Config.in
> ksrc/skins/uitron/Kconfig
> ksrc/skins/uitron/Makefile
ksrc/skins/uitron/COPYING
> ksrc/skins/vrtx/Config.in
> ksrc/skins/vrtx/Kconfig
> ksrc/skins/vrtx/Makefile
> ksrc/skins/vrtx/defs.h
> ksrc/skins/vrtx/event.c
> ksrc/skins/vrtx/event.h
> ksrc/skins/vrtx/heap.c
> ksrc/skins/vrtx/heap.h
> ksrc/skins/vrtx/mb.c
> ksrc/skins/vrtx/mb.h
> ksrc/skins/vrtx/module.c
> ksrc/skins/vrtx/mx.c
> ksrc/skins/vrtx/mx.h
> ksrc/skins/vrtx/pt.c
> ksrc/skins/vrtx/pt.h
> ksrc/skins/vrtx/queue.c
> ksrc/skins/vrtx/queue.h
> ksrc/skins/vrtx/sem.c
> ksrc/skins/vrtx/sem.h
> ksrc/skins/vrtx/task.c
> ksrc/skins/vrtx/task.h
> ksrc/skins/vrtx/time.c
ksrc/skins/vrtx/COPyING
> ksrc/skins/vxworks/Config.in
> ksrc/skins/vxworks/Kconfig
> ksrc/skins/vxworks/Makefile
> ksrc/skins/vxworks/defs.h
> ksrc/skins/vxworks/demos/Makefile
> ksrc/skins/vxworks/errnoLib.c
> ksrc/skins/vxworks/intLib.c
> ksrc/skins/vxworks/kernelLib.c
> ksrc/skins/vxworks/module.c
> ksrc/skins/vxworks/msgQLib.c
> ksrc/skins/vxworks/semLib.c
> ksrc/skins/vxworks/sysLib.c
> ksrc/skins/vxworks/taskHookLib.c
> ksrc/skins/vxworks/taskInfo.c
> ksrc/skins/vxworks/taskLib.c
> ksrc/skins/vxworks/tickLib.c
> ksrc/skins/vxworks/wdLib.c
ksrc/skins/vxworks/COPYING
> scripts/Kconfig.frag
> scripts/Makefile.am
> scripts/Modules.frag
> scripts/bootstrap
> scripts/defconfig.frag
> scripts/help_from_kconfig.pl
> scripts/histo.gp
> scripts/prepare-kernel.sh
> scripts/wrap-link.sh
> scripts/xeno-config.in
> scripts/xeno.in
No idea
> src/Makefile.am
> src/drvlib/Makefile.am
> src/drvlib/analogy/Makefile.am
> src/include/Makefile.am
> src/include/xeno_config.h.in
> src/skins/Makefile.am
> src/skins/common/Makefile.am
No idea
> src/skins/native/Makefile.am
> src/skins/native/libxenomai_native.pc.in
> src/skins/native/wrappers.h
src/skins/native/COPYING
> src/skins/posix/Makefile.am
> src/skins/posix/libxenomai_posix.pc.in
> src/skins/posix/posix.wrappers
src/skins/posix/COPYING
> src/skins/psos+/Makefile.am
> src/skins/psos+/libxenomai_psos+.pc.in
No idea
> src/skins/rtdm/Makefile.am
> src/skins/rtdm/libxenomai_rtdm.pc.in
src/skins/rtdm/COPYING
> src/skins/uitron/Makefile.am
> src/skins/uitron/libxenomai_uitron.pc.in
No idea
> src/skins/vrtx/Makefile.am
> src/skins/vrtx/libxenomai_vrtx.pc.in
> src/skins/vrtx/wrappers.h
src/skins/vrtx/COPYING
> src/skins/vxworks/Makefile.am
> src/skins/vxworks/libxenomai_vxworks.pc.in
> src/skins/vxworks/wrappers.h
src/skins/vxworks/COPYING
> src/testsuite/Makefile.am
> src/testsuite/clocktest/Makefile.am
> src/testsuite/cyclic/Makefile.am
> src/testsuite/irqbench/Makefile.am
> src/testsuite/klatency/Makefile.am
> src/testsuite/latency/Makefile.am
> src/testsuite/latency/latency.c
> src/testsuite/regression/Makefile.am
> src/testsuite/regression/native+posix/Makefile.am
> src/testsuite/regression/native/Makefile.am
> src/testsuite/regression/posix/Makefile.am
> src/testsuite/regression/posix/xddp_test.c
> src/testsuite/regression/xeno-regression-test.in
> src/testsuite/switchtest/Makefile.am
> src/testsuite/unit/Makefile.am
> src/testsuite/unit/check-vdso.c
> src/testsuite/unit/wakeup-time.c
> src/testsuite/xeno-test/Makefile.am
> src/testsuite/xeno-test/dohell
> src/testsuite/xeno-test/xeno-test-run-wrapper
> src/testsuite/xeno-test/xeno-test.in
> src/utils/Makefile.am
> src/utils/analogy/Makefile.am
> src/utils/analogy/wf_facilities.c
> src/utils/analogy/wf_facilities.h
> src/utils/can/Makefile.am
> src/utils/can/README
> src/utils/ps/Makefile.am
> src/utils/ps/rtps.c
No idea.
> Have no license defined or i have not found it. Please, could you put some
> lines to clarify that?
Well clearly a lot of the directories have a COPYING file, but a few
do not.
So I see 163 files that I have no idea out of 342 files, so 179 do seem
to have a clear license stated. That seems to solve about half the
question just by looking in the directories. Doesn't answer the other
half though.
--
Len Sorensen
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-17 16:25 [Xenomai] License Issues Leopold Palomo-Avellaneda
2015-06-17 16:48 ` Lennart Sorensen
@ 2015-06-17 17:25 ` Gilles Chanteperdrix
2015-06-17 21:35 ` Leopold Palomo-Avellaneda
1 sibling, 1 reply; 14+ messages in thread
From: Gilles Chanteperdrix @ 2015-06-17 17:25 UTC (permalink / raw)
To: Leopold Palomo-Avellaneda; +Cc: xenomai
Leopold Palomo-Avellaneda wrote:
> Hi,
>
> using a debian tool to check the license of the package I have found that
> his
> files:
This mail looks very different from the one you sent me privately and I
told you to post on the list. It does not even concern the same version of
Xenomai.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-17 17:25 ` Gilles Chanteperdrix
@ 2015-06-17 21:35 ` Leopold Palomo-Avellaneda
2015-06-18 6:59 ` Jan Kiszka
0 siblings, 1 reply; 14+ messages in thread
From: Leopold Palomo-Avellaneda @ 2015-06-17 21:35 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix va
escriure:
> Leopold Palomo-Avellaneda wrote:
> > Hi,
> >
> > using a debian tool to check the license of the package I have found that
> > his
>
> > files:
> This mail looks very different from the one you sent me privately and I
> told you to post on the list. It does not even concern the same version of
> Xenomai.
yes,
it's true. But what I understood from you was that it was better that I sent
to the list. That file comes from xenomai-2.6.4. Any problem then?
I just need to clarify this kind of things because ftp-masters are every day
more strict (what I think it's better), especially with licenses. Never
happens nothing till the day that something happen.
If can check this kind of stuff it would be better, that's all. For instance, I
was a bit surprised about the autotools generated files, because I thought they
would never had license.
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150617/33bdf053/attachment.sig>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-17 16:48 ` Lennart Sorensen
@ 2015-06-17 21:36 ` Leopold Palomo-Avellaneda
0 siblings, 0 replies; 14+ messages in thread
From: Leopold Palomo-Avellaneda @ 2015-06-17 21:36 UTC (permalink / raw)
To: Lennart Sorensen; +Cc: xenomai
El Dimecres, 17 de juny de 2015, a les 12:48:13, Lennart Sorensen va escriure:
> On Wed, Jun 17, 2015 at 06:25:05PM +0200, Leopold Palomo-Avellaneda wrote:
> > Hi,
> >
> > using a debian tool to check the license of the package I have found that
> > his
> > files:
> Well here is my guess based on reading what is there. And besides who
> says all files have to mention the license themselves? The directory
> could have that info or the entire project.
>
> > examples/Makefile
> > examples/common/Makefile
> > examples/native/Makefile
> > examples/native/rtprint.c
> > examples/native/sigdebug.c
> > examples/native/trivial-periodic.c
> > examples/posix/Makefile
> > examples/posix/README
> > examples/rtdm/driver-api/Makefile
> > examples/rtdm/profiles/can/Makefile
> > examples/rtdm/profiles/ipc/Makefile
> > examples/rtdm/profiles/ipc/bufp-label.c
> > examples/rtdm/profiles/ipc/bufp-readwrite.c
> > examples/rtdm/profiles/ipc/iddp-label.c
> > examples/rtdm/profiles/ipc/iddp-sendrecv.c
> > examples/rtdm/profiles/ipc/xddp-echo.c
> > examples/rtdm/profiles/ipc/xddp-label.c
> > examples/rtdm/profiles/ipc/xddp-stream.c
> > examples/rtdm/profiles/serial/Makefile
>
> No idea.
>
> > include/Makefile.am
> > include/analogy/Makefile.am
> > include/asm-arm/Makefile.am
> > include/asm-arm/bits/Makefile.am
> > include/asm-blackfin/Makefile.am
> > include/asm-blackfin/bits/Makefile.am
> > include/asm-blackfin/bits/bind.h
> > include/asm-blackfin/fptest.h
> > include/asm-generic/Makefile.am
> > include/asm-generic/bits/Makefile.am
> > include/asm-generic/pci_ids.h
> > include/asm-nios2/Makefile.am
> > include/asm-nios2/bits/Makefile.am
> > include/asm-nios2/bits/bind.h
> > include/asm-nios2/fptest.h
> > include/asm-powerpc/Makefile.am
> > include/asm-powerpc/bits/Makefile.am
> > include/asm-powerpc/bits/bind.h
> > include/asm-powerpc/fptest.h
> > include/asm-sh/Makefile.am
> > include/asm-sh/bits/Makefile.am
> > include/asm-sh/bits/bind.h
> > include/asm-sh/fptest.h
> > include/asm-sim/Makefile.am
> > include/asm-sim/bits/Makefile.am
> > include/asm-x86/Makefile.am
> > include/asm-x86/arith.h
> > include/asm-x86/bits/Makefile.am
> > include/asm-x86/bits/pod.h
> > include/asm-x86/features.h
> > include/asm-x86/switch.h
> > include/asm-x86/system.h
> > include/asm-x86/wrappers.h
> > include/compat/asm-i386/io_ports.h
> > include/compat/linux/calc64.h
> > include/native/Makefile.am
> > include/nucleus/Makefile.am
> > include/nucleus/seqlock.h
> > include/posix/Makefile.am
> > include/posix/sys/Makefile.am
> > include/psos+/Makefile.am
> > include/psos+/long_names.h
> > include/rtdm/Makefile.am
> > include/testing/sigtest_syscall.h
> > include/uitron/Makefile.am
> > include/vrtx/Makefile.am
> > include/vrtx/vrtx.h
> > include/vxworks/Makefile.am
> > include/vxworks/vxworks.h
>
> Seems to be covered by include/COPYING
>
> > ksrc/Config.in
> > ksrc/Makefile
> > ksrc/arch/Makefile
> > ksrc/arch/arm/Kconfig
> > ksrc/arch/arm/Makefile
> > ksrc/arch/arm/patches/README
> > ksrc/arch/arm/patches/beaglebone/ipipe-core-3.8.13-beaglebone-p
> > ost.patch
> > ksrc/arch/arm/patches/beaglebone/ipipe-core-3.8.13-beaglebone-p
> > re.patch
> > ksrc/arch/arm/patches/ipipe-core-3.10.32-arm-5.patch
> > ksrc/arch/arm/patches/ipipe-core-3.8.13-arm-4.patch
> > ksrc/arch/arm/patches/raspberry/ipipe-core-3.8.13-raspberry-pos
> > t-2.patch
> > ksrc/arch/arm/patches/raspberry/ipipe-core-3.8.13-raspberry-pre
> > -2.patch
> > ksrc/arch/arm/patches/zynq/ipipe-core-3.5.7-zynq-post.patch
> > ksrc/arch/arm/patches/zynq/ipipe-core-3.5.7-zynq-pre.patch
> > ksrc/arch/arm/patches/zynq/ipipe-core-3.8-zynq-post.patch
> > ksrc/arch/arm/patches/zynq/ipipe-core-3.8-zynq-pre.patch
> > ksrc/arch/blackfin/Config.in
> > ksrc/arch/blackfin/Kconfig
> > ksrc/arch/blackfin/Makefile
> > ksrc/arch/blackfin/patches/README
> > ksrc/arch/blackfin/patches/ipipe-core-3.10.32-blackfin-3.patch
> > ksrc/arch/blackfin/patches/ipipe-core-3.14.17-blackfin-4.patch
> > ksrc/arch/blackfin/patches/ipipe-core-3.8.13-blackfin-2.patch
> > ksrc/arch/generic/Makefile
> > ksrc/arch/generic/compat.c
> > ksrc/arch/nios2/Config.in
> > ksrc/arch/nios2/Kconfig
> > ksrc/arch/nios2/Makefile
> > ksrc/arch/nios2/patches/README
> > ksrc/arch/powerpc/Config.in
> > ksrc/arch/powerpc/Kconfig
> > ksrc/arch/powerpc/Makefile
> > ksrc/arch/powerpc/patches/README
> > ksrc/arch/powerpc/patches/ipipe-core-3.10.32-powerpc-4.patch
> > ksrc/arch/powerpc/patches/ipipe-core-3.14.17-powerpc-4.patch
> > ksrc/arch/powerpc/patches/ipipe-core-3.8.13-powerpc-2.patch
> > ksrc/arch/sh/Kconfig
> > ksrc/arch/sh/Makefile
> > ksrc/arch/sh/patches/README
> > ksrc/arch/x86/Config.in
> > ksrc/arch/x86/Kconfig
> > ksrc/arch/x86/Makefile
> > ksrc/arch/x86/patches/README
> > ksrc/arch/x86/patches/ipipe-core-3.10.32-x86-4.patch
> > ksrc/arch/x86/patches/ipipe-core-3.14.17-x86-4.patch
> > ksrc/arch/x86/patches/ipipe-core-3.8.13-x86-4.patch
> > ksrc/drivers/Config.in
> > ksrc/drivers/Kconfig
> > ksrc/drivers/Makefile
> > ksrc/drivers/analogy/Config.in
> > ksrc/drivers/analogy/Kconfig
> > ksrc/drivers/analogy/Makefile
> > ksrc/drivers/analogy/intel/Config.in
> > ksrc/drivers/analogy/intel/Kconfig
> > ksrc/drivers/analogy/intel/Makefile
> > ksrc/drivers/analogy/national_instruments/Config.in
> > ksrc/drivers/analogy/national_instruments/Kconfig
> > ksrc/drivers/analogy/national_instruments/Makefile
> > ksrc/drivers/analogy/sensoray/Config.in
> > ksrc/drivers/analogy/sensoray/Kconfig
> > ksrc/drivers/analogy/sensoray/Makefile
> > ksrc/drivers/analogy/testing/Config.in
> > ksrc/drivers/analogy/testing/Kconfig
> > ksrc/drivers/analogy/testing/Makefile
> > ksrc/drivers/analogy/testing/fake.c
> > ksrc/drivers/can/CREDITS
> > ksrc/drivers/can/Config.in
> > ksrc/drivers/can/Kconfig
> > ksrc/drivers/can/Makefile
> > ksrc/drivers/can/README
> > ksrc/drivers/can/mscan/Config.in
> > ksrc/drivers/can/mscan/Kconfig
> > ksrc/drivers/can/mscan/Makefile
> > ksrc/drivers/can/mscan/rtcan_mscan.c
> > ksrc/drivers/can/mscan/rtcan_mscan_mpc52xx.c
> > ksrc/drivers/can/rtcan_internal.h
> > ksrc/drivers/can/rtcan_module.c
> > ksrc/drivers/can/sja1000/Config.in
> > ksrc/drivers/can/sja1000/Kconfig
> > ksrc/drivers/can/sja1000/Makefile
> > ksrc/drivers/can/sja1000/rtcan_esd_pci.c
> > ksrc/drivers/can/sja1000/rtcan_peak_dng.c
> > ksrc/drivers/can/sja1000/rtcan_peak_pci.c
> > ksrc/drivers/can/sja1000/rtcan_plx_pci.c
> > ksrc/drivers/ipc/Config.in
> > ksrc/drivers/ipc/Kconfig
> > ksrc/drivers/ipc/Makefile
> > ksrc/drivers/serial/Config.in
> > ksrc/drivers/serial/Kconfig
> > ksrc/drivers/serial/Makefile
> > ksrc/drivers/testing/Config.in
> > ksrc/drivers/testing/Kconfig
> > ksrc/drivers/testing/Makefile
> > ksrc/drivers/testing/sigtest_module.c
>
> No idea. Although given it is applied as a patch to a linux kernel,
> one would think GPLv2 is the only option it could be under.
>
> > ksrc/nucleus/Config.in
> > ksrc/nucleus/Kconfig
> > ksrc/nucleus/Makefile
> > ksrc/nucleus/udev/rtheap.rules
> > ksrc/nucleus/udev/rtpipe.rules
>
> ksrc/nucleus/COPYING
>
> > ksrc/skins/Config.in
> > ksrc/skins/Kconfig
> > ksrc/skins/Makefile
> > ksrc/skins/native/API.CHANGES
> > ksrc/skins/native/Config.in
> > ksrc/skins/native/Kconfig
> > ksrc/skins/native/Makefile
> > ksrc/skins/native/demos/Makefile
> > ksrc/skins/native/demos/latency.c
> > ksrc/skins/native/demos/satch.c
> > ksrc/skins/native/snippets/bound_task.c
> > ksrc/skins/native/snippets/cond_var.c
> > ksrc/skins/native/snippets/event_flags.c
> > ksrc/skins/native/snippets/kernel_task.c
> > ksrc/skins/native/snippets/local_heap.c
> > ksrc/skins/native/snippets/msg_queue.c
> > ksrc/skins/native/snippets/mutex.c
> > ksrc/skins/native/snippets/pipe.c
> > ksrc/skins/native/snippets/semaphore.c
> > ksrc/skins/native/snippets/shared_mem.c
> > ksrc/skins/native/snippets/sigxcpu.c
> > ksrc/skins/native/snippets/user_alarm.c
> > ksrc/skins/native/snippets/user_irq.c
> > ksrc/skins/native/snippets/user_task.c
>
> ksrc/skins/native/COPYING
>
> > ksrc/skins/posix/Config.in
> > ksrc/skins/posix/Kconfig
> > ksrc/skins/posix/Makefile
> > ksrc/skins/posix/apc.h
> > ksrc/skins/posix/cancel.c
> > ksrc/skins/posix/cancel.h
> > ksrc/skins/posix/cb_lock.h
> > ksrc/skins/posix/clock.c
> > ksrc/skins/posix/cond.c
> > ksrc/skins/posix/cond.h
> > ksrc/skins/posix/cond_attr.c
> > ksrc/skins/posix/demos/Kbuild
> > ksrc/skins/posix/demos/Makefile
> > ksrc/skins/posix/demos/accuracy.c
> > ksrc/skins/posix/internal.h
> > ksrc/skins/posix/module.c
> > ksrc/skins/posix/mq.c
> > ksrc/skins/posix/mq.h
> > ksrc/skins/posix/mutex.c
> > ksrc/skins/posix/mutex.h
> > ksrc/skins/posix/mutex_attr.c
> > ksrc/skins/posix/once.c
> > ksrc/skins/posix/registry.c
> > ksrc/skins/posix/registry.h
> > ksrc/skins/posix/sched.c
> > ksrc/skins/posix/sem.c
> > ksrc/skins/posix/sem.h
> > ksrc/skins/posix/shm.h
> > ksrc/skins/posix/sig.h
> > ksrc/skins/posix/signal.c
> > ksrc/skins/posix/thread.c
> > ksrc/skins/posix/thread.h
> > ksrc/skins/posix/thread_attr.c
> > ksrc/skins/posix/tsd.c
> > ksrc/skins/posix/tsd.h
>
> ksrc/skins/posix/COPYING
>
> > ksrc/skins/psos+/API.CHANGES
> > ksrc/skins/psos+/Config.in
> > ksrc/skins/psos+/Kconfig
> > ksrc/skins/psos+/Makefile
> > ksrc/skins/psos+/demos/Makefile
>
> ksrc/skins/psos+/COPYING
>
> > ksrc/skins/rtdm/API.CHANGES
> > ksrc/skins/rtdm/Config.in
> > ksrc/skins/rtdm/Kconfig
> > ksrc/skins/rtdm/Makefile
>
> ksrc/skins/rtdm/COPYING
>
> > ksrc/skins/uitron/Config.in
> > ksrc/skins/uitron/Kconfig
> > ksrc/skins/uitron/Makefile
>
> ksrc/skins/uitron/COPYING
>
> > ksrc/skins/vrtx/Config.in
> > ksrc/skins/vrtx/Kconfig
> > ksrc/skins/vrtx/Makefile
> > ksrc/skins/vrtx/defs.h
> > ksrc/skins/vrtx/event.c
> > ksrc/skins/vrtx/event.h
> > ksrc/skins/vrtx/heap.c
> > ksrc/skins/vrtx/heap.h
> > ksrc/skins/vrtx/mb.c
> > ksrc/skins/vrtx/mb.h
> > ksrc/skins/vrtx/module.c
> > ksrc/skins/vrtx/mx.c
> > ksrc/skins/vrtx/mx.h
> > ksrc/skins/vrtx/pt.c
> > ksrc/skins/vrtx/pt.h
> > ksrc/skins/vrtx/queue.c
> > ksrc/skins/vrtx/queue.h
> > ksrc/skins/vrtx/sem.c
> > ksrc/skins/vrtx/sem.h
> > ksrc/skins/vrtx/task.c
> > ksrc/skins/vrtx/task.h
> > ksrc/skins/vrtx/time.c
>
> ksrc/skins/vrtx/COPyING
>
> > ksrc/skins/vxworks/Config.in
> > ksrc/skins/vxworks/Kconfig
> > ksrc/skins/vxworks/Makefile
> > ksrc/skins/vxworks/defs.h
> > ksrc/skins/vxworks/demos/Makefile
> > ksrc/skins/vxworks/errnoLib.c
> > ksrc/skins/vxworks/intLib.c
> > ksrc/skins/vxworks/kernelLib.c
> > ksrc/skins/vxworks/module.c
> > ksrc/skins/vxworks/msgQLib.c
> > ksrc/skins/vxworks/semLib.c
> > ksrc/skins/vxworks/sysLib.c
> > ksrc/skins/vxworks/taskHookLib.c
> > ksrc/skins/vxworks/taskInfo.c
> > ksrc/skins/vxworks/taskLib.c
> > ksrc/skins/vxworks/tickLib.c
> > ksrc/skins/vxworks/wdLib.c
>
> ksrc/skins/vxworks/COPYING
>
> > scripts/Kconfig.frag
> > scripts/Makefile.am
> > scripts/Modules.frag
> > scripts/bootstrap
> > scripts/defconfig.frag
> > scripts/help_from_kconfig.pl
> > scripts/histo.gp
> > scripts/prepare-kernel.sh
> > scripts/wrap-link.sh
> > scripts/xeno-config.in
> > scripts/xeno.in
>
> No idea
>
> > src/Makefile.am
> > src/drvlib/Makefile.am
> > src/drvlib/analogy/Makefile.am
> > src/include/Makefile.am
> > src/include/xeno_config.h.in
> > src/skins/Makefile.am
> > src/skins/common/Makefile.am
>
> No idea
>
> > src/skins/native/Makefile.am
> > src/skins/native/libxenomai_native.pc.in
> > src/skins/native/wrappers.h
>
> src/skins/native/COPYING
>
> > src/skins/posix/Makefile.am
> > src/skins/posix/libxenomai_posix.pc.in
> > src/skins/posix/posix.wrappers
>
> src/skins/posix/COPYING
>
> > src/skins/psos+/Makefile.am
> > src/skins/psos+/libxenomai_psos+.pc.in
>
> No idea
>
> > src/skins/rtdm/Makefile.am
> > src/skins/rtdm/libxenomai_rtdm.pc.in
>
> src/skins/rtdm/COPYING
>
> > src/skins/uitron/Makefile.am
> > src/skins/uitron/libxenomai_uitron.pc.in
>
> No idea
>
> > src/skins/vrtx/Makefile.am
> > src/skins/vrtx/libxenomai_vrtx.pc.in
> > src/skins/vrtx/wrappers.h
>
> src/skins/vrtx/COPYING
>
> > src/skins/vxworks/Makefile.am
> > src/skins/vxworks/libxenomai_vxworks.pc.in
> > src/skins/vxworks/wrappers.h
>
> src/skins/vxworks/COPYING
>
> > src/testsuite/Makefile.am
> > src/testsuite/clocktest/Makefile.am
> > src/testsuite/cyclic/Makefile.am
> > src/testsuite/irqbench/Makefile.am
> > src/testsuite/klatency/Makefile.am
> > src/testsuite/latency/Makefile.am
> > src/testsuite/latency/latency.c
> > src/testsuite/regression/Makefile.am
> > src/testsuite/regression/native+posix/Makefile.am
> > src/testsuite/regression/native/Makefile.am
> > src/testsuite/regression/posix/Makefile.am
> > src/testsuite/regression/posix/xddp_test.c
> > src/testsuite/regression/xeno-regression-test.in
> > src/testsuite/switchtest/Makefile.am
> > src/testsuite/unit/Makefile.am
> > src/testsuite/unit/check-vdso.c
> > src/testsuite/unit/wakeup-time.c
> > src/testsuite/xeno-test/Makefile.am
> > src/testsuite/xeno-test/dohell
> > src/testsuite/xeno-test/xeno-test-run-wrapper
> > src/testsuite/xeno-test/xeno-test.in
> > src/utils/Makefile.am
> > src/utils/analogy/Makefile.am
> > src/utils/analogy/wf_facilities.c
> > src/utils/analogy/wf_facilities.h
> > src/utils/can/Makefile.am
> > src/utils/can/README
> > src/utils/ps/Makefile.am
> > src/utils/ps/rtps.c
>
> No idea.
>
> > Have no license defined or i have not found it. Please, could you put some
> > lines to clarify that?
>
> Well clearly a lot of the directories have a COPYING file, but a few
> do not.
>
> So I see 163 files that I have no idea out of 342 files, so 179 do seem
> to have a clear license stated. That seems to solve about half the
> question just by looking in the directories. Doesn't answer the other
> half though.
Thanks Lennart,
you did the half of the work!!!
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150617/07dd047a/attachment.sig>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-17 21:35 ` Leopold Palomo-Avellaneda
@ 2015-06-18 6:59 ` Jan Kiszka
2015-06-18 7:05 ` Gilles Chanteperdrix
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Jan Kiszka @ 2015-06-18 6:59 UTC (permalink / raw)
To: Leopold Palomo-Avellaneda, Gilles Chanteperdrix; +Cc: xenomai
On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
> El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix va
> escriure:
>> Leopold Palomo-Avellaneda wrote:
>>> Hi,
>>>
>>> using a debian tool to check the license of the package I have found that
>>> his
>>
>>> files:
>> This mail looks very different from the one you sent me privately and I
>> told you to post on the list. It does not even concern the same version of
>> Xenomai.
>
> yes,
>
> it's true. But what I understood from you was that it was better that I sent
> to the list. That file comes from xenomai-2.6.4. Any problem then?
>
> I just need to clarify this kind of things because ftp-masters are every day
> more strict (what I think it's better), especially with licenses. Never
> happens nothing till the day that something happen.
Out of curiosity: How do these license check work right now? What's the
tool used and how are the outputs processed (manual or automatic
decisions etc.)?
>
> If can check this kind of stuff it would be better, that's all. For instance, I
> was a bit surprised about the autotools generated files, because I thought they
> would never had license.
If something has no license, it cannot be used. IIRC, you can freely
choose the license of the generated autotools files, but you should
state at least something somewhere to avoid needless confusion for
people who validate the licenses of projects (AKA license clearing process).
Given that tool-based license analysis often looks at individual files
only, a license header for those that lack a note would be the optimal
resolution. The minimum - and likely the only option for generated files
- is to define a default license for Xenomai that covers all files not
explicitly carrying a note or not being covered by a subdir COPYING file.
Did you also look at Xenomai 3 already in this regard, Leopold?
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 6:59 ` Jan Kiszka
@ 2015-06-18 7:05 ` Gilles Chanteperdrix
2015-06-18 7:18 ` Philippe Gerum
2015-06-18 7:19 ` Jan Kiszka
2015-06-18 8:03 ` Gilles Chanteperdrix
2015-06-18 8:46 ` Leopold Palomo-Avellaneda
2 siblings, 2 replies; 14+ messages in thread
From: Gilles Chanteperdrix @ 2015-06-18 7:05 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
Jan Kiszka wrote:
> On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
>> El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix va
>> escriure:
>>> Leopold Palomo-Avellaneda wrote:
>>>> Hi,
>>>>
>>>> using a debian tool to check the license of the package I have found
>>>> that
>>>> his
>>>
>>>> files:
>>> This mail looks very different from the one you sent me privately and I
>>> told you to post on the list. It does not even concern the same version
>>> of
>>> Xenomai.
>>
>> yes,
>>
>> it's true. But what I understood from you was that it was better that I
>> sent
>> to the list. That file comes from xenomai-2.6.4. Any problem then?
>>
>> I just need to clarify this kind of things because ftp-masters are every
>> day
>> more strict (what I think it's better), especially with licenses. Never
>> happens nothing till the day that something happen.
>
> Out of curiosity: How do these license check work right now? What's the
> tool used and how are the outputs processed (manual or automatic
> decisions etc.)?
>
>>
>> If can check this kind of stuff it would be better, that's all. For
>> instance, I
>> was a bit surprised about the autotools generated files, because I
>> thought they
>> would never had license.
>
> If something has no license, it cannot be used.
That is an over-simplification. Or maybe a policy of the company you work
at. But that is not a general truth that applies to everyone.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 7:05 ` Gilles Chanteperdrix
@ 2015-06-18 7:18 ` Philippe Gerum
2015-06-18 7:19 ` Jan Kiszka
1 sibling, 0 replies; 14+ messages in thread
From: Philippe Gerum @ 2015-06-18 7:18 UTC (permalink / raw)
To: Gilles Chanteperdrix, Jan Kiszka; +Cc: xenomai
On 06/18/2015 09:05 AM, Gilles Chanteperdrix wrote:
>
> Jan Kiszka wrote:
>> On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
>>> El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix va
>>> escriure:
>>>> Leopold Palomo-Avellaneda wrote:
>>>>> Hi,
>>>>>
>>>>> using a debian tool to check the license of the package I have found
>>>>> that
>>>>> his
>>>>
>>>>> files:
>>>> This mail looks very different from the one you sent me privately and I
>>>> told you to post on the list. It does not even concern the same version
>>>> of
>>>> Xenomai.
>>>
>>> yes,
>>>
>>> it's true. But what I understood from you was that it was better that I
>>> sent
>>> to the list. That file comes from xenomai-2.6.4. Any problem then?
>>>
>>> I just need to clarify this kind of things because ftp-masters are every
>>> day
>>> more strict (what I think it's better), especially with licenses. Never
>>> happens nothing till the day that something happen.
>>
>> Out of curiosity: How do these license check work right now? What's the
>> tool used and how are the outputs processed (manual or automatic
>> decisions etc.)?
>>
>>>
>>> If can check this kind of stuff it would be better, that's all. For
>>> instance, I
>>> was a bit surprised about the autotools generated files, because I
>>> thought they
>>> would never had license.
>>
>> If something has no license, it cannot be used.
>
> That is an over-simplification. Or maybe a policy of the company you work
> at. But that is not a general truth that applies to everyone.
>
>
I believe Jan refers to the default copyright laws in this case, which
state that all copyrights are retained by the author.
--
Philippe.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 7:05 ` Gilles Chanteperdrix
2015-06-18 7:18 ` Philippe Gerum
@ 2015-06-18 7:19 ` Jan Kiszka
2015-06-18 7:25 ` Gilles Chanteperdrix
1 sibling, 1 reply; 14+ messages in thread
From: Jan Kiszka @ 2015-06-18 7:19 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
On 2015-06-18 09:05, Gilles Chanteperdrix wrote:
>
> Jan Kiszka wrote:
>> On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
>>> El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix va
>>> escriure:
>>>> Leopold Palomo-Avellaneda wrote:
>>>>> Hi,
>>>>>
>>>>> using a debian tool to check the license of the package I have found
>>>>> that
>>>>> his
>>>>
>>>>> files:
>>>> This mail looks very different from the one you sent me privately and I
>>>> told you to post on the list. It does not even concern the same version
>>>> of
>>>> Xenomai.
>>>
>>> yes,
>>>
>>> it's true. But what I understood from you was that it was better that I
>>> sent
>>> to the list. That file comes from xenomai-2.6.4. Any problem then?
>>>
>>> I just need to clarify this kind of things because ftp-masters are every
>>> day
>>> more strict (what I think it's better), especially with licenses. Never
>>> happens nothing till the day that something happen.
>>
>> Out of curiosity: How do these license check work right now? What's the
>> tool used and how are the outputs processed (manual or automatic
>> decisions etc.)?
>>
>>>
>>> If can check this kind of stuff it would be better, that's all. For
>>> instance, I
>>> was a bit surprised about the autotools generated files, because I
>>> thought they
>>> would never had license.
>>
>> If something has no license, it cannot be used.
>
> That is an over-simplification. Or maybe a policy of the company you work
> at. But that is not a general truth that applies to everyone.
Of course, it's a simplification (you may still use it secretly under
your blanket), but your lawyer will tell you something like this if you
ask. At least when referring to common copyright laws on this planet. So
this is not a company policy thing but a jurisdiction issue.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 7:19 ` Jan Kiszka
@ 2015-06-18 7:25 ` Gilles Chanteperdrix
2015-06-18 7:41 ` Jan Kiszka
0 siblings, 1 reply; 14+ messages in thread
From: Gilles Chanteperdrix @ 2015-06-18 7:25 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
Jan Kiszka wrote:
> On 2015-06-18 09:05, Gilles Chanteperdrix wrote:
>>
>> Jan Kiszka wrote:
>>> On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
>>>> El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix
>>>> va
>>>> escriure:
>>>>> Leopold Palomo-Avellaneda wrote:
>>>>>> Hi,
>>>>>>
>>>>>> using a debian tool to check the license of the package I have found
>>>>>> that
>>>>>> his
>>>>>
>>>>>> files:
>>>>> This mail looks very different from the one you sent me privately and
>>>>> I
>>>>> told you to post on the list. It does not even concern the same
>>>>> version
>>>>> of
>>>>> Xenomai.
>>>>
>>>> yes,
>>>>
>>>> it's true. But what I understood from you was that it was better that
>>>> I
>>>> sent
>>>> to the list. That file comes from xenomai-2.6.4. Any problem then?
>>>>
>>>> I just need to clarify this kind of things because ftp-masters are
>>>> every
>>>> day
>>>> more strict (what I think it's better), especially with licenses.
>>>> Never
>>>> happens nothing till the day that something happen.
>>>
>>> Out of curiosity: How do these license check work right now? What's the
>>> tool used and how are the outputs processed (manual or automatic
>>> decisions etc.)?
>>>
>>>>
>>>> If can check this kind of stuff it would be better, that's all. For
>>>> instance, I
>>>> was a bit surprised about the autotools generated files, because I
>>>> thought they
>>>> would never had license.
>>>
>>> If something has no license, it cannot be used.
>>
>> That is an over-simplification. Or maybe a policy of the company you
>> work
>> at. But that is not a general truth that applies to everyone.
>
> Of course, it's a simplification (you may still use it secretly under
> your blanket), but your lawyer will tell you something like this if you
> ask. At least when referring to common copyright laws on this planet. So
> this is not a company policy thing but a jurisdiction issue.
What I mean is that there are other cases, such as:
- code in the public domain
- reuse of portions of the code that fall under "fair use" or "right to
quote", that could easily apply to things like the 5 lines x86 arith.h or
the examples. And I would think that of the Makefiles too.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 7:25 ` Gilles Chanteperdrix
@ 2015-06-18 7:41 ` Jan Kiszka
0 siblings, 0 replies; 14+ messages in thread
From: Jan Kiszka @ 2015-06-18 7:41 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
On 2015-06-18 09:25, Gilles Chanteperdrix wrote:
>
> Jan Kiszka wrote:
>> On 2015-06-18 09:05, Gilles Chanteperdrix wrote:
>>>
>>> Jan Kiszka wrote:
>>>> On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
>>>>> El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix
>>>>> va
>>>>> escriure:
>>>>>> Leopold Palomo-Avellaneda wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> using a debian tool to check the license of the package I have found
>>>>>>> that
>>>>>>> his
>>>>>>
>>>>>>> files:
>>>>>> This mail looks very different from the one you sent me privately and
>>>>>> I
>>>>>> told you to post on the list. It does not even concern the same
>>>>>> version
>>>>>> of
>>>>>> Xenomai.
>>>>>
>>>>> yes,
>>>>>
>>>>> it's true. But what I understood from you was that it was better that
>>>>> I
>>>>> sent
>>>>> to the list. That file comes from xenomai-2.6.4. Any problem then?
>>>>>
>>>>> I just need to clarify this kind of things because ftp-masters are
>>>>> every
>>>>> day
>>>>> more strict (what I think it's better), especially with licenses.
>>>>> Never
>>>>> happens nothing till the day that something happen.
>>>>
>>>> Out of curiosity: How do these license check work right now? What's the
>>>> tool used and how are the outputs processed (manual or automatic
>>>> decisions etc.)?
>>>>
>>>>>
>>>>> If can check this kind of stuff it would be better, that's all. For
>>>>> instance, I
>>>>> was a bit surprised about the autotools generated files, because I
>>>>> thought they
>>>>> would never had license.
>>>>
>>>> If something has no license, it cannot be used.
>>>
>>> That is an over-simplification. Or maybe a policy of the company you
>>> work
>>> at. But that is not a general truth that applies to everyone.
>>
>> Of course, it's a simplification (you may still use it secretly under
>> your blanket), but your lawyer will tell you something like this if you
>> ask. At least when referring to common copyright laws on this planet. So
>> this is not a company policy thing but a jurisdiction issue.
>
> What I mean is that there are other cases, such as:
> - code in the public domain
> - reuse of portions of the code that fall under "fair use" or "right to
> quote", that could easily apply to things like the 5 lines x86 arith.h or
> the examples. And I would think that of the Makefiles too.
You may not be wrong, depending on the concrete case, but relying on
such assumptions needlessly complicates licensing for the end user,
specifically those that carefully check license obligations and
compatibilities. It's way simpler for everyone to make the licensing
intention of the copyright holder explicit, even for "trivial" code.
It's already way simpler than having such a discussion. ;)
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 6:59 ` Jan Kiszka
2015-06-18 7:05 ` Gilles Chanteperdrix
@ 2015-06-18 8:03 ` Gilles Chanteperdrix
2015-06-18 8:05 ` Gilles Chanteperdrix
2015-06-18 8:46 ` Leopold Palomo-Avellaneda
2 siblings, 1 reply; 14+ messages in thread
From: Gilles Chanteperdrix @ 2015-06-18 8:03 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
Jan Kiszka wrote:
> resolution. The minimum - and likely the only option for generated files
Just checked. Comments in Makefile.am are passed verbatim in Makefile.in.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 8:03 ` Gilles Chanteperdrix
@ 2015-06-18 8:05 ` Gilles Chanteperdrix
0 siblings, 0 replies; 14+ messages in thread
From: Gilles Chanteperdrix @ 2015-06-18 8:05 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: Jan Kiszka, xenomai
Gilles Chanteperdrix wrote:
>
> Jan Kiszka wrote:
>> resolution. The minimum - and likely the only option for generated files
>
> Just checked. Comments in Makefile.am are passed verbatim in Makefile.in.
>
Well, actually the generated Makefile.in have a copyright added by automake.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xenomai] License Issues
2015-06-18 6:59 ` Jan Kiszka
2015-06-18 7:05 ` Gilles Chanteperdrix
2015-06-18 8:03 ` Gilles Chanteperdrix
@ 2015-06-18 8:46 ` Leopold Palomo-Avellaneda
2 siblings, 0 replies; 14+ messages in thread
From: Leopold Palomo-Avellaneda @ 2015-06-18 8:46 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
Hi,
I leave my desktop a few minutes and I got this bunch of messages!!!!
El Dijous, 18 de juny de 2015, a les 08:59:25, Jan Kiszka va escriure:
> On 2015-06-17 23:35, Leopold Palomo-Avellaneda wrote:
> > El Dimecres, 17 de juny de 2015, a les 19:25:56, Gilles Chanteperdrix va
> >
> > escriure:
> >> Leopold Palomo-Avellaneda wrote:
> >>> Hi,
> >>>
> >>> using a debian tool to check the license of the package I have found
> >>> that
> >>> his
> >>
> >>> files:
> >> This mail looks very different from the one you sent me privately and I
> >> told you to post on the list. It does not even concern the same version
> >> of
> >> Xenomai.
> >
> > yes,
> >
> > it's true. But what I understood from you was that it was better that I
> > sent to the list. That file comes from xenomai-2.6.4. Any problem then?
> >
> > I just need to clarify this kind of things because ftp-masters are every
> > day more strict (what I think it's better), especially with licenses.
> > Never happens nothing till the day that something happen.
>
> Out of curiosity: How do these license check work right now? What's the
> tool used and how are the outputs processed (manual or automatic
> decisions etc.)?
I use debmake [1] (debmake -ccc). I normally create a debian package from
zero, using some templates of similar from packages. The job that makes me
spend more time is the copyright file and make it almost lintian [2] clean. I
have attached the files generated. Anyway, debmake makes a good job.
The copyright file, in the format:
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
has some fields. Basically, you must put, after the header:
Files: (which files)
Copyright: (who holds the copyright. Take note that not the author. Many
times, you could have an author that work for a company and the copyright
belongs to the company)
License: (a key of the license) [3]
It helps me to fill the final copyright file. For instance, I know that the
doc directory is GFDL-1.2 (at least it was on 2.6.3), so all the references to
doc/* I put then under Files: doc/* manually.
Also, there are cases that for instance the tool show:
Files: ksrc/drivers/analogy/national_instruments/mio_common.c
Copyright: 1997-2001 David A. Schleef <ds@schleef.org>
2002-2006 Frank Mori Hess <fmhess@users.sourceforge.net>
License: __UNKNOWN__
This code is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published
by the Free Software Foundation; either version 2 of the License,
or (at your option) any later version.
the tool mark that files as __UNKNOWN__, but in the body of the license you
can read that it's GPL-2.0+
Obviously, edit all that files and put the same header, format, whatever will
help. It's a manual, tedious and boring job.
>
> > If can check this kind of stuff it would be better, that's all. For
> > instance, I was a bit surprised about the autotools generated files,
> > because I thought they would never had license.
>
> If something has no license, it cannot be used. IIRC, you can freely
> choose the license of the generated autotools files, but you should
> state at least something somewhere to avoid needless confusion for
> people who validate the licenses of projects (AKA license clearing process).
>
> Given that tool-based license analysis often looks at individual files
> only, a license header for those that lack a note would be the optimal
> resolution. The minimum - and likely the only option for generated files
> - is to define a default license for Xenomai that covers all files not
> explicitly carrying a note or not being covered by a subdir COPYING file.
>
> Did you also look at Xenomai 3 already in this regard, Leopold?
Yes, I put both files from xenomai-3 git and xenomai-2.6 git.
I know that is a lot of disgusting work, to check all the files, see the
header, or whatever, but, at least for xenomai-3 could be good.
Another thing could be write a file explaining every directory license. I
think that the kernel patches are GPL-2.0 but the library are LGPL2.1, but I
don't know which directories are from one or other, of if they are mixed. In
xenomai-2.6 is not done.
In Xenomai-3, the web says:
"For information regarding a particular software component, you should look at
the COPYING file available in the directory containing the relevant source
code."
but:
$../xenomai-3.git$ ls
config demo include lib README testsuite configure.ac debian
doc kernel Makefile.am scripts utils
$../xenomai-3.git$ tree -fia | grep COPYING
./include/COPYING
./kernel/cobalt/COPYING
./kernel/cobalt/posix/COPYING
./kernel/cobalt/rtdm/COPYING
./lib/alchemy/COPYING
./lib/analogy/COPYING
./lib/cobalt/COPYING
./lib/copperplate/COPYING
./lib/psos/COPYING
./lib/vxworks/COPYING
doc, config, utils, scripts, testsuite, debian* and demo directories have not
COPYING files.
I have admit that I began to work with 2.6.4, but looking this it seems more
easy (in license terms) to manage this issue with xenomai-3. :-) (And no
Gilles, it's not a waste of time. A lot of people use 2.6.x, like me for
instance)
Best regards,
Leopold
[1] http://anonscm.debian.org/cgit/collab-maint/debmake.git
[2] Lintian is a tool used to check the quality of a debian package. It try to
make it following all the debian policies.
[3] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#stand-alone-license-paragraph
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: copyright-xenomai-2.6-debug.zip
Type: application/zip
Size: 34442 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150618/dbdbc425/attachment.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: copyrights-xenomai3-debug.zip
Type: application/zip
Size: 44039 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150618/dbdbc425/attachment-0001.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150618/dbdbc425/attachment.sig>
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2015-06-18 8:46 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-17 16:25 [Xenomai] License Issues Leopold Palomo-Avellaneda
2015-06-17 16:48 ` Lennart Sorensen
2015-06-17 21:36 ` Leopold Palomo-Avellaneda
2015-06-17 17:25 ` Gilles Chanteperdrix
2015-06-17 21:35 ` Leopold Palomo-Avellaneda
2015-06-18 6:59 ` Jan Kiszka
2015-06-18 7:05 ` Gilles Chanteperdrix
2015-06-18 7:18 ` Philippe Gerum
2015-06-18 7:19 ` Jan Kiszka
2015-06-18 7:25 ` Gilles Chanteperdrix
2015-06-18 7:41 ` Jan Kiszka
2015-06-18 8:03 ` Gilles Chanteperdrix
2015-06-18 8:05 ` Gilles Chanteperdrix
2015-06-18 8:46 ` Leopold Palomo-Avellaneda
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.