On Sun, Mar 18, 2018 at 01:31:05PM +0800, Paul Wise wrote:
> On Sun, 2018-03-18 at 01:50 +0000, Chris Lamb wrote:
>
> > I am unsure that a debian/ directory plus the upstream source really
> > creates a derived work.
>
> It definitely does when there are patches to the upstream code in
> debian/, which is the case I'm talking about with this feature request.
>...
What is supposed to be checked here,
and how should that be fixed outside
the trivial case where all upstream
files are under the same licence?
As an example, think of a kernel patch that touches two files:
1. source file with SPDX-License-Identifier: GPL-2.0
2. userspace header with SPDX-License-Identifier: GPL-2.0 WITH
Linux-syscall-note
"same license as upstream" are two different licences for different
parts of the patch, and the Debian kernel maintainer is usually not
the author of a patch cherry-picked from upstream.
Want copyright information do you want to make mandatory for patches
in src:linux?
DEP-5 listing of every patch, and for patches like the example above a
detailed explanation which parts of a patch are under which licence?
IMHO it would be more reasonable to treat debian/patches/
as special case, defaulting to "same licence as the patched code".
> bye,
> pabs
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
