From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] app-crypt/kstart License questionable
Date: Fri, 9 May 2008 13:00:31 -0700 [thread overview]
Message-ID: <20080509200030.GC3847@comet> (raw)
In-Reply-To: <20080509191030.GB20481@mephisto>
On 21:10 Fri 09 May , Michael Hammer wrote:
> Hi!
>
> I'd like to add kstart to the tree and have a question to the license
> of the package. It's some kind of combination of the MIT License with
> a few minor licenses. Should I add the whole license file to the tree?
> Here is the link:
>
> http://www.eyrie.org/~eagle/software/kstart/license.html
>
> There is a very similar situation on the sys-auth/pam_krb5 package
> which is also from Russ Allbery. There we provide not the full license
> needed for the package.
It's nicest if you can map each license back to an individual one in the
tree. People generally ignore the build system when doing that. When
doing the licensing thing, the way things seem to go in Gentoo is to get
the actual license language mapped to a license file but ignore any
differences in copyright ownership (e.g., Stanford vs X Consortium).
Thanks,
Donnie
--
gentoo-dev@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-05-09 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 19:10 [gentoo-dev] app-crypt/kstart License questionable Michael Hammer
2008-05-09 20:00 ` Donnie Berkholz [this message]
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=20080509200030.GC3847@comet \
--to=dberkholz@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