From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: licenses@gentoo.org, Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-dev] Guidance on distributed patented software
Date: Tue, 21 Sep 2021 17:25:40 +0200 [thread overview]
Message-ID: <2054816.G923GbCHz0@noumea> (raw)
In-Reply-To: <CAGfcS_knT99Q63FKZA0L-NOd9wHs7i261TLQxivyy=m1DHut8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
Am Montag, 20. September 2021, 19:27:37 CEST schrieb Rich Freeman:
> On Mon, Sep 20, 2021 at 12:46 PM Alec Warner <antarus@gentoo.org> wrote:
> > 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?
>
> I think you have the gist of it. Is there actually anything in the
> repo these days which is patent-encumbered?
media-libs/openh264 for example
(It right now prevents me from building firefox and chromium for the
experimental binary package hosting [1], since I blanket mask everything with
bindist restriction. That is likely a bit of overkill, it would be enough to
not make any binary package from it (which ends up being distributed), but
that function needs to still be programmed in portage.)
[1] Blog post with details coming soon. Please wait for it before asking
questions.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, qa, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-21 15:26 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 [this message]
2021-09-20 18:30 ` [gentoo-dev] " Ulrich Mueller
2021-09-26 6:38 ` Alec Warner
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=2054816.G923GbCHz0@noumea \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=licenses@gentoo.org \
--cc=rich0@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