All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: Morten Linderud <foxboron@archlinux.org>
Cc: "Michał Górny" <mgorny@gentoo.org>, distributions@lists.linux.dev
Subject: Re: Looking for advice on how to deal with potential slop packages
Date: Sat, 07 Mar 2026 16:31:18 +0100	[thread overview]
Message-ID: <878qc38xmh.fsf@josefsson.org> (raw)
In-Reply-To: <aawYbre5_xvhfwKA@framework> (Morten Linderud's message of "Sat, 7 Mar 2026 13:36:18 +0100")

[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]

Morten Linderud <foxboron@archlinux.org> writes:

> A lot of this is probably already a lost cause I think.

+1

I wonder if there is even consensus to refuse to package AI-rewritten
packages with a different license, such as python-chardet:

https://github.com/chardet/chardet/issues/327
https://github.com/chardet/chardet/issues/331

I think that is a separate category of LLM contributions, unlike the
LLM-assistance used for many years in the Linux kernel.

If AI-rewrites for copyright reasons becomes common, that is problematic
for a free software perspective.  One recurse is to actively chose to
not use such rewrites, but to insist on using copyleft packages as a
policy and preference in order to defend user's rights.

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.  It is possible
to offer an alternative but it requires an active choice and interested
developers/users.

/Simon

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1251 bytes --]

  reply	other threads:[~2026-03-07 15:58 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 [this message]
2026-03-08  4:00     ` Guillem Jover
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=878qc38xmh.fsf@josefsson.org \
    --to=simon@josefsson.org \
    --cc=distributions@lists.linux.dev \
    --cc=foxboron@archlinux.org \
    --cc=mgorny@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 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.