From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Installing COPYING or LICENSE files
Date: Tue, 27 Dec 2005 12:32:25 +0200 [thread overview]
Message-ID: <43B11839.4060804@gentoo.org> (raw)
In-Reply-To: <20051227085357.GA4151@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
Harald van Dijk wrote:
> On Tue, Dec 27, 2005 at 01:01:10AM -0600, R Hill wrote:
>
>>>Removing these files and relying on LICENSE=foo in the ebuild could be seen as
>>>a copyright violation. There are lots of samples in /usr/src/licenses that
>>>aren't generic, but include a copyright notice naming the authors of a
>>>particular piece of software, but it doesn't match with all packages under
>>>this license of course. Take ZLIB as example. Since I'm not a lawyer I might
>>>be wrong, but me thinks it would make sense to ask one.
>>
>>AFAIK most licenses need to be included with the distribution of the source, not
>>installed on the system after compilation. But I could be wrong too.
>
>
> There are exceptions, a popular one being BSD.
>
> * 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.
>
> As a quick example, iputils is BSD-licensed and does not install or
> reproduce its license, so does this cause problems for iputils binpkgs?
We are not redistributing anything in binary form when installing
programs. This all happens on the users computers. We are distributing
upstream source tarballs verbatim of course. If the license should be
installed, shouldn't the upstream make install take care of it then?
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-12-27 10:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 7:12 [gentoo-dev] aging ebuilds with unstable keywords Daniel Ahlberg
2005-11-14 13:14 ` Andrej Kacian
2005-11-21 2:39 ` [gentoo-dev] " R Hill
2005-11-21 12:47 ` Petteri Räty
2005-12-26 13:24 ` [gentoo-dev] Installing COPYING or LICENSE files Petteri Räty
2005-12-26 13:57 ` Drake Wyrm
2005-12-26 14:02 ` Petteri Räty
2005-12-26 14:12 ` Diego 'Flameeyes' Pettenò
2005-12-26 14:21 ` Carsten Lohrke
2005-12-27 7:01 ` [gentoo-dev] " R Hill
2005-12-27 7:08 ` Mike Frysinger
2005-12-27 7:23 ` Brian Harring
2005-12-27 7:33 ` Mike Frysinger
2005-12-27 13:14 ` Carsten Lohrke
2005-12-27 8:53 ` Harald van Dijk
2005-12-27 10:32 ` Petteri Räty [this message]
2005-12-27 11:20 ` Harald van Dijk
2005-12-27 14:57 ` Henrik Brix Andersen
2005-12-27 13:40 ` Harald van Dijk
2005-12-26 20:48 ` [gentoo-dev] " Mike Frysinger
2005-12-27 13:43 ` Petteri Räty
2005-11-25 7:16 ` [gentoo-dev] Re: aging ebuilds with unstable keywords Andrej Kacian
2005-11-25 23:15 ` R Hill
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=43B11839.4060804@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-dev@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