From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-licenses@lists.gentoo.org
Subject: [gentoo-licenses] handling copyright attribution in licenses that require it
Date: Thu, 27 Mar 2014 04:04:27 -0400 [thread overview]
Message-ID: <7300519.hgbMOkFsuE@vapier> (raw)
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
if you want to utilize the LICENSE variable in ebuilds to help with licensing
compliance, you quickly run into issues with the licenses that require
explicit copyright attribution. specifically, the BSD and MIT family of
licenses. this clause is the annoying part:
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
since all of the ebuilds point to the same stock file (e.g. licenses/BSD)
which has this stock header:
Copyright (c) <YEAR>, <OWNER>
the file is not sufficient for automatically producing a file that covers all
packages in a compliant manner.
in Chromium OS, we're attacking the problem in two ways:
- during build (when all the source is available), scan for copyright
owners and save the results into the vdb
- allow for people to override on a per-package basis in the
licenses/copyright-attribution/ subdir
the first option would be nice to integrate into portage, but there are going
to be cases where it either cannot find all the right answers (because the
source doesn't correctly state it), or might find too many wrong answers
(unused source files with outdated names). so we're going to want to
integrate this somehow on a per-ebuild basis. metadata.xml might work, but
doesn't work well with something that can change across ebuild $PVR's. so
maybe something like a new LICENSE_COPYRIGHT variable that can be a scalar or
array.
has anyone else been looking at this ? or have thoughts on how to tackle the
problem in a non-sucky way ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-03-27 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 8:04 Mike Frysinger [this message]
2014-03-28 8:01 ` [gentoo-licenses] handling copyright attribution in licenses that require it Ulrich Mueller
2014-03-28 17:13 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7300519.hgbMOkFsuE@vapier \
--to=vapier@gentoo.org \
--cc=gentoo-licenses@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox