From: Ryan Shaw <ryan.shaw@stanfordalumni.org>
To: gentoo-dev@gentoo.org
Cc: sandymac@gentoo.org
Subject: Re: [gentoo-dev] LICENSE??
Date: Thu, 16 May 2002 13:13:17 +0900 [thread overview]
Message-ID: <20020516131317.6d73f65e.ryan.shaw@stanfordalumni.org> (raw)
In-Reply-To: <3CE25FA4.2080306@gentoo.org>
William wrote:
> 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, LICENSE="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.
The original text of the license is in Japanese. The Debian
package of the software in question (lha) has the following translation:
It's free to distribute on the network, but if you distribute for
the people who cannot access the network (by magazine or CD-ROM),
please send E-Mail (Inter-Net address) to the author before the
distribution. That's well where this software is appeard.
If you cannot do, you must send me the E-Mail later.
Original Source Code License Statement:
/* Copyright (C) MCMLXXXIX Yooichi.Tagawa */
/* Modified Nobutaka Watazaki */
/* Thanks to H.Yoshizaki. (MS-DOS LHarc) */
As far as I understand it, there is permission to distribute but
not to modify, due to patent issues[*].
Ryan
[*]http://google.com/search?q=cache:www.cpe.surrey.ac.uk/support/faq/gif_lzw.htm
next prev parent reply other threads:[~2002-05-16 4:17 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
2002-05-16 4:13 ` Ryan Shaw [this message]
-- 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=20020516131317.6d73f65e.ryan.shaw@stanfordalumni.org \
--to=ryan.shaw@stanfordalumni.org \
--cc=gentoo-dev@gentoo.org \
--cc=sandymac@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