From: Guillem Jover <guillem@debian.org>
To: Simon Josefsson <simon@josefsson.org>
Cc: "Morten Linderud" <foxboron@archlinux.org>,
"Michał Górny" <mgorny@gentoo.org>,
distributions@lists.linux.dev
Subject: Re: Looking for advice on how to deal with potential slop packages
Date: Sun, 8 Mar 2026 05:00:33 +0100 [thread overview]
Message-ID: <aaz0Yb3SOXmxiJ5l@thunder.hadrons.org> (raw)
In-Reply-To: <878qc38xmh.fsf@josefsson.org>
On Sat, 2026-03-07 at 16:31:18 +0100, Simon Josefsson wrote:
> To some extent we already see this split, between copyleft-aligned
> GNU/Linux distributions like Guix that default to GnuPG and GNU
> coreutils, and some commercial distributions that is on a path to
> replace all GPL'd code.
>
> Given that we couldn't establish such consensus in the pre-AI times (for
> GnuPG vs Seqoia and GNU coreutils vs uutils), and there even seem to
> some preference towards the non-copyleft agenda, I think the same will
> happen again for AI-rewrites.
>
> The commercial dynamic is pro LLM and against copyleft. […]
I'm not sure why you felt the need to drag the GnuPG issue here in
this context, when that's already messy enough.
The reason many upstream projects and distributions are distancing
themselves from GnuPG (at various speeds), is a thing of GnuPG's
upstream own making. There's been long standing concerns about its
UI, security and implementation. Mishandling the OpenPGP RFC process
and then subsequently getting off it, and not just refusing to implement
it but in addition creating a schism and a fork in the ecosystem did
not help matters, which is what has triggered many to seriously look
into alternative OpenPGP implementations (which thankfully we have many
to choose from now!). All this has had no relation whatsoever with
licensing.
(BTW and AFAIR most of Sequoia components are either LGPL or GPL.)
Regards,
Guillem
next prev parent reply other threads:[~2026-03-08 4:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 10:38 Looking for advice on how to deal with potential slop packages Michał Górny
2026-03-07 12:07 ` Noé Lopez
2026-03-07 12:36 ` Morten Linderud
2026-03-07 15:31 ` Simon Josefsson
2026-03-08 4:00 ` Guillem Jover [this message]
2026-03-22 23:53 ` Andreas K. Huettel
2026-03-23 8:14 ` Simon Josefsson
2026-03-11 2:48 ` Sam James
2026-03-11 2:50 ` Sam James
2026-03-27 8:01 ` Bernhard M. Wiedemann
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=aaz0Yb3SOXmxiJ5l@thunder.hadrons.org \
--to=guillem@debian.org \
--cc=distributions@lists.linux.dev \
--cc=foxboron@archlinux.org \
--cc=mgorny@gentoo.org \
--cc=simon@josefsson.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 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.