public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Clarify the "as-is" license?
Date: Mon, 24 Sep 2012 09:02:37 +0200	[thread overview]
Message-ID: <20576.1421.973743.531319@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAGfcS_mJr1+eU6zmaRsbuZQQZrCjgaOSkX8omNLmh40kvfCN5w@mail.gmail.com>

>>>>> On Sun, 23 Sep 2012, Rich Freeman wrote:

>> - net-misc/ntp: "as-is" looks fine as main license, although some
>> parts of the code are under different licenses like GPL (but I
>> haven't checked in detail what gets installed).

> Uh, if we're distributing the sources, and they contain GPL content,
> then the only valid answer is GPL,

Unfortunately, it's not clear from our documentation if the LICENSE
variable applies to the source tarball or to the files that the
package installs on the user's system.

I tend to interpret it in the latter sense. To illustrate why, let's
look at sci-visualization/gnuplot-4.6.0 as an example:

   LICENSE="gnuplot GPL-2 bitmap? ( free-noncomm )"

The bulk of the package is free software, distributed under the
gnuplot license or the GPL-2. However, there's an additional notice
with a no-sale clause in a single source file (src/bitmap.c).
If LICENSE applies to installed files, than we can disable the
functionality via USE=-bitmap and we're done.

However, if we say that LICENSE covers the source tarball, then we
either need to change it to an unconditional "gnuplot GPL-2
free-noncomm", which has the consequence that gnuplot is no longer
installable for users who have ACCEPT_LICENSE="-* @FREE".

Or, we must no longer distribute pristine source from upstream, but
repack them into a new tarball with bitmap.c removed. This would have
to be done for every release, which isn't feasible.

Similar reasoning applies to the various Linux kernel packages that
have LICENSE="GPL-2 !deblob? ( freedist )".

> or nomirror.

That's a different issue. In the case of RESTRICT="mirror" it is clear
that it applies to the sources that we distribute.

Ulrich


  reply	other threads:[~2012-09-24  7:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-23 10:56 [gentoo-dev] Clarify the "as-is" license? Ulrich Mueller
2012-09-23 11:15 ` Rich Freeman
2012-09-23 12:04   ` Ulrich Mueller
2012-09-23 12:10     ` hasufell
2012-09-23 21:37       ` Ulrich Mueller
2012-09-24  0:36         ` Rich Freeman
2012-09-24  7:02           ` Ulrich Mueller [this message]
2012-09-24 10:46             ` Rich Freeman
2012-09-24 13:15               ` Ulrich Mueller
2012-09-24 13:20               ` Ian Stakenvicius
2012-09-24  2:10         ` Alexandre Rostovtsev
2012-09-24 13:01       ` Ian Stakenvicius
2012-09-24 13:15         ` Chí-Thanh Christopher Nguyễn
2012-09-24 13:25           ` Ian Stakenvicius
2012-09-24 13:48           ` Ulrich Mueller
2012-09-29 19:27             ` Chí-Thanh Christopher Nguyễn
2012-09-25 11:04 ` [gentoo-dev] " Ulrich Mueller
2012-09-25 15:30   ` Diego Elio Pettenò
2012-09-25 18:12     ` Ulrich Mueller
2012-09-25 15:55   ` Alexandre Rostovtsev
2012-09-25 17:14     ` Rich Freeman
2012-09-29 19:27   ` Chí-Thanh Christopher Nguyễn
2012-09-29 21:21     ` Ulrich Mueller
2012-09-29 23:38       ` Rich Freeman
2012-10-03 21:18         ` lists
2013-01-03 14:39         ` [gentoo-dev] Packages without source code (was: Clarify the "as-is" license?) Ulrich Mueller
2013-01-03 15:40           ` Rich Freeman
2013-01-03 22:58             ` [gentoo-dev] " Duncan
2014-04-23  9:39             ` [gentoo-dev] Packages without source code Ulrich Mueller
2012-10-06 14:14   ` [gentoo-dev] Re: Clarify the "as-is" license? Ulrich Mueller
2012-10-06 15:24     ` Duncan
2012-11-01 10:12   ` Ulrich Mueller
2014-05-19  8:57     ` [gentoo-dev] Removal of the as-is (so-called) license Ulrich Mueller
2014-05-19  9:08       ` Alexander Berntsen
2014-05-19 18:58       ` hasufell
2014-05-25 14:40       ` [gentoo-dev] " Ulrich Mueller

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=20576.1421.973743.531319@a1i15.kph.uni-mainz.de \
    --to=ulm@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