public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Gentoo Dev <gentoo-dev@lists.gentoo.org>, licenses@gentoo.org
Subject: [gentoo-dev] Re: Guidance on distributed patented software
Date: Sat, 25 Sep 2021 23:38:45 -0700	[thread overview]
Message-ID: <CAAr7Pr8HVFr0mPaZUp6R5xqnL2nLhpdaRX+cTVNMazGUEZ7C6Q@mail.gmail.com> (raw)
In-Reply-To: <uo88np0av@gentoo.org>

On Mon, Sep 20, 2021 at 11:30 AM Ulrich Mueller <ulm@gentoo.org> wrote:
>
> >>>>> On Mon, 20 Sep 2021, Alec Warner wrote:
>
> > The devmanual discusses licensing as a core concept
> > (https://devmanual.gentoo.org/general-concepts/licenses/index.html)
> > but does not cover patents. My understanding is that we:
>
> >  - set RESTRICT=bindist when we are unable to redistribute binaries
> > (e.g. due to a license or patent restriction.)
> >  - set RESTRICT=mirror when we are unable to redistribute source code
> > (e.g. due to a license of patent restriction.)
>
> IANAL, but IIUC patents only apply to programs that can run on a
> computer. This is the case for binaries but not for source code.
>
> In other words, we don't need mirror restriction for source tarballs
> because of patents.
>
> >  - Sometimes, we remove patent encumbered source code from packages
> > (e.g. with USE=bindist) so that we can build redistributable binaries
> > with the patented features removed.
>
> We do, but normally this doesn't prevent us from distributing the source
> code.

Great, I'll send a patch to devmanual to add details about how we
treat patented software in Gentoo (the original goal of the thread; I
don't care what happens to openssl as much ;p)

-A

>
> > Could we add some text to the license concepts covering patents? It
> > seems to have been omitted?
> > Is my understanding of how we manage patented software correct?


      reply	other threads:[~2021-09-26  6:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 16:46 [gentoo-dev] Guidance on distributed patented software Alec Warner
2021-09-20 17:27 ` Rich Freeman
2021-09-20 18:15   ` Robin H. Johnson
2021-09-20 18:41     ` Ulrich Mueller
2021-09-20 19:20       ` Robin H. Johnson
2021-09-22 12:54     ` Joshua Kinard
2021-09-22 16:37       ` Robin H. Johnson
2021-09-23  5:54         ` Joshua Kinard
2021-09-23 15:52           ` Peter Stuge
     [not found]           ` <CAAr7Pr9a6cRbHDxkUbKwxabW8skh1izA7C2GqTE1XF8mg-CV0g@mail.gmail.com>
2021-09-24  7:46             ` Joshua Kinard
     [not found]               ` <20210924095510.6ff13620@computer>
2021-09-25 19:44                 ` Joshua Kinard
2021-09-26 17:09                   ` Peter Stuge
2021-09-26 19:20                     ` Rich Freeman
2021-09-27 18:14                       ` Marek Szuba
2021-09-27 21:09                         ` Rich Freeman
2021-09-26 19:41                   ` Sam James
2021-09-21 15:25   ` Andreas K. Huettel
2021-09-20 18:30 ` [gentoo-dev] " Ulrich Mueller
2021-09-26  6:38   ` Alec Warner [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=CAAr7Pr8HVFr0mPaZUp6R5xqnL2nLhpdaRX+cTVNMazGUEZ7C6Q@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=licenses@gentoo.org \
    --cc=ulm@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