From: David Leverton <levertond@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Add operator + for licenses (EAPI-4 ?)
Date: Fri, 4 Sep 2009 19:52:11 +0100 [thread overview]
Message-ID: <200909041952.12314.levertond@googlemail.com> (raw)
In-Reply-To: <4AA12BD5.8060108@gentoo.org>
On Friday 04 September 2009 16:01:41 Rémi Cardona wrote:
> For instance, I'm still working on migrating all the X11 packages to the
> "MIT" license (mainly for cleaning purposes), but in fact, each and
> every package should have its own license file (like today) because the
> MIT license requires that we acknowledge all major contributions to the
> code. Therefore, using a template like ${PORTAGE}/licences/MIT does is
> probably not a good idea from a legal point of view.
Is that really a problem? I admit to not being around for the original design
decisions, but I would assume that the purpose of having LICENSE in ebuilds
is to tell users what licence the package is under (whether or not it's
accurate is a different matter), and the purpose of having the licences
themselves in the tree is so that it's easy for users to look them up and
decide whether they want to accept the conditions or not. For that purpose,
the exact list of credits is irrelevant. Also, I'm not a lawyer, but I would
think that the licence's requirement for credit is satisfied by the credits
being included in the source code - it doesn't require acknowledgement when
merely talking about the software or stating the fact that it's under a
particular licence, just when distributing it.
next prev parent reply other threads:[~2009-09-04 13:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 22:12 [gentoo-dev] [RFC] Add operator + for licenses (EAPI-4 ?) Mounir Lamouri
2009-08-31 22:30 ` Rémi Cardona
2009-09-03 20:50 ` Mounir Lamouri
2009-09-01 2:21 ` Sebastian Pipping
2009-09-01 5:54 ` [gentoo-dev] " Duncan
2009-09-03 21:10 ` Mounir Lamouri
2009-09-03 21:15 ` Rémi Cardona
2009-09-03 21:27 ` Mounir Lamouri
2009-09-04 4:53 ` Duncan
2009-09-04 15:01 ` Rémi Cardona
2009-09-04 18:52 ` David Leverton [this message]
2009-09-04 20:04 ` Rémi Cardona
2009-09-04 20:08 ` Ciaran McCreesh
2009-09-05 14:03 ` Maciej Mrozowski
2009-09-05 15:02 ` Ciaran McCreesh
2009-09-06 0:34 ` Thomas Anderson
2009-09-06 6:31 ` Rémi Cardona
2009-09-03 21:08 ` [gentoo-dev] " Mounir Lamouri
2009-09-04 21:11 ` Sebastian Pipping
2009-09-05 1:06 ` Zac Medico
2009-09-05 8:40 ` [gentoo-dev] " Duncan
2009-09-05 9:28 ` [gentoo-dev] " Ulrich Mueller
2009-09-05 10:59 ` Zac Medico
2009-09-05 17:21 ` Mounir Lamouri
2009-09-05 18:41 ` Ulrich Mueller
2009-09-06 0:14 ` Sebastian Pipping
2009-09-05 21:37 ` Zac Medico
2009-10-01 2:01 ` Sebastian Pipping
2009-10-01 13:09 ` volkmar
2009-09-04 15:47 ` Jeremy Olexa
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=200909041952.12314.levertond@googlemail.com \
--to=levertond@googlemail.com \
--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