From: Vagrant Cascadian <vagrant@debian.org>
To: 34717@debbugs.gnu.org
Cc: guix-devel@gnu.org
Subject: Re: bug#34717: GPL and Openssl incompatibilities in u-boot and possibly others
Date: Fri, 22 Oct 2021 14:17:33 -0700 [thread overview]
Message-ID: <87cznwoj2q.fsf@yucca> (raw)
In-Reply-To: <87y26loa74.fsf@yucca>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On 2021-10-21, Vagrant Cascadian wrote:
> For the last couple years guix has been applying simple workarounds in
> u-boot packages to disable the features that required openssl due to
> GPL/openssl license incompatibilities.
>
> I made an attempt at updating guix to u-boot 2021.10, which seems to
> have made openssl harder to workaround... many of the u-boot-BOARD
> packages now require it, and the previous workarounds to disable openssl
> in u-boot-tools seem ineffective.
>
> I see a few ways forward:
>
> * Dig deeper into figuring out how to disable the workarounds...
>
> * Refactor the code that uses openssl to use an alternate
> implementation. Upstream would welcome the fixes, at least in
> theory. Most promising candidate might be wolfssl, last I looked, but
> it may miss some features.
>
> * Convince upstream u-boot to relicense relevent GPLed portions of code
> with an openssl exception. Upstream is dubious about this being
> practical, largely due to the sheer number of potential contributors
> who would have to agree to it.
* Disable substitutes for relevent packages. Technically correct as
license incompatibility is only triggered on transmission of binary,
though maybe missing something about the spirit of the GPL.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-10-22 21:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 1:58 bug#34717: GPL and Openssl incompatibilities in u-boot and possibly others Vagrant Cascadian
2019-03-06 15:15 ` Ludovic Courtès
2019-03-06 18:12 ` Danny Milosavljevic
2019-03-08 9:59 ` Ludovic Courtès
2019-03-07 4:17 ` Vagrant Cascadian
2019-03-07 23:02 ` Vagrant Cascadian
2019-03-08 10:23 ` Ludovic Courtès
2019-03-08 19:14 ` Vagrant Cascadian
2019-03-09 21:57 ` Ludovic Courtès
2019-03-09 23:10 ` Vagrant Cascadian
2019-03-10 3:58 ` Jack Hill
2019-03-10 17:12 ` Ludovic Courtès
2021-10-22 6:17 ` Vagrant Cascadian
2021-10-22 20:35 ` Leo Famulari
2021-10-22 21:15 ` Vagrant Cascadian
2021-10-23 9:08 ` Maxime Devos
2021-10-22 21:17 ` Vagrant Cascadian [this message]
2021-10-23 19:44 ` Leo Famulari
2021-10-24 8:50 ` Dr. Arne Babenhauserheide
2019-03-08 10:08 ` Ludovic Courtès
2019-03-08 10:16 ` Ludovic Courtès
2019-03-15 23:55 ` Adonay Felipe Nogueira
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=87cznwoj2q.fsf@yucca \
--to=vagrant@debian.org \
--cc=34717@debbugs.gnu.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.