public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: <lists@aixah.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Clarify the "as-is" license?
Date: Wed, 3 Oct 2012 23:18:27 +0200	[thread overview]
Message-ID: <20121003231827.7d7260d0@gentp> (raw)
In-Reply-To: <CAGfcS_kS4-fBveFs_4x1mhs+i3LZt6afgQnH9AqUKnYazp7N2Q@mail.gmail.com>

On Sat, 29 Sep 2012 19:38:50 -0400
Rich Freeman <rich0@gentoo.org> wrote:

> On Sat, Sep 29, 2012 at 5:21 PM, Ulrich Mueller <ulm@gentoo.org>
> wrote:
> The license isn't binary-only.  The license is BSD.  It just happens
> that the thing they're licensing is the binary and not the source.
> 
> Does it really matter?  Before we start overloading the LICENSE flag
> to represent something other than the license we should probably have
> a problem to actually fix.
> 
> As far as freedom of code goes, arguably the code is perfectly free -
> it just isn't open source.  You could legally decompile, modify,
> recompile, and redistribute it and your assembly language sources as
> much as you like.

Imho software as it's described here shouldn't get a LICENSE which is
in @FREE, such as BSD.

For a software to be free, it has to be possible to change it in any
way you want. And "to be possible" and "to be allowed" really aren't
the same here! (Except if you are either masochistic or one of these
gurus which eat assembly code for breakfast).

I have an ACCEPT_LICENSE="-* @FREE" in my make.conf, so I expect that
there's only free software on my system (except for those packages I
explicitly allowed via package.license, for sure). I couldn't make this
assumption anymore if software as you describe it would get a @FREE
LICENSE.

Cheers,
aranea


  reply	other threads:[~2012-10-03 21:19 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
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 [this message]
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=20121003231827.7d7260d0@gentp \
    --to=lists@aixah.de \
    --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