From: William McArthur <sandymac@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] LICENSE=???
Date: Wed, 15 May 2002 09:16:20 -0400 [thread overview]
Message-ID: <3CE25FA4.2080306@gentoo.org> (raw)
In-Reply-To: 20020515181304.356cb5af.ryan.shaw@stanfordalumni.org
Ryan Shaw wrote:
> What should the LICENSE variable be set to when
> creating an ebuild for software with a weird or
> unknown license?
That depends, LICENCSE="Foo" where "Foo" is a filename in
/usr/portage/licenses/ . Foo should match the file name exactly.
There is a special case called "as-is" please read it for details on it.
If the licenses is truly unique then we need to add another one to the
directory.
If you need logic for more than one license use | for or logic and ( and
) for grouping. And logic is implied if no other operator is used. eg:
LICENSE="GPL-2 | ( LGPL-2.1 Foo )"
The above would mean, The pacakges requires the user agreee to the GPL
v2 licenser OR both of the LGPL v2.1 and Foo licenses.
Sandy McArthur
next prev parent reply other threads:[~2002-05-15 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 9:13 [gentoo-dev] LICENSE=??? Ryan Shaw
2002-05-15 13:16 ` William McArthur [this message]
2002-05-16 4:13 ` [gentoo-dev] LICENSE?? Ryan Shaw
-- strict thread matches above, loose matches on Subject: below --
2001-05-25 12:01 [gentoo-dev] license? Matt.Wilkie
2001-05-25 12:28 ` Daniel Robbins
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=3CE25FA4.2080306@gentoo.org \
--to=sandymac@gentoo.org \
--cc=gentoo-dev@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