I share this opinion as well. What should we do about getting license information on the Kconfig files?
--Brennan On Sun, Jan 19, 2020, 11:01 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > What about the Kconfig files and the defconf files? > > I see Linux now has license information (but not copyrights) in their > Kconfig files. For example > https://elixir.bootlin.com/linux/latest/source/Kconfig : > > # SPDX-License-Identifier: GPL-2.0 > # > # For a description of the syntax of this configuration file, > # see Documentation/kbuild/kconfig-language.rst. > # > > But defconfig files do not. For example, > > https://elixir.bootlin.com/linux/v5.4.13/source/arch/arm/configs/am200epdkit_defconfig > . > > I tend to agree with the way Linux does things. Kconfig files require > manual effort to generate and maintain and are a work that should be > protected. defconfig files, on the other hand, are auto-generated and > you want people to be free to use them. And how would you copyright or > license and auto-generated file that anyone can create/re-create by > running a tool. Certainly, if they re-created the identical file (as > the tool would with idential selections), that identical file would not > have derived for the original defconfig in any way. > > And since the defconfig file is auto generated, it would have to have an > auto generated license and copyright. That is, I think the wrong way to > go. But that is just an opinion. > > > >
