From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Morten Linderud <foxboron@archlinux.org>,
Simon Josefsson <simon@josefsson.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: Mon, 23 Mar 2026 00:53:45 +0100 [thread overview]
Message-ID: <2081671.zToM8qfIzz@noumea> (raw)
In-Reply-To: <878qc38xmh.fsf@josefsson.org>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Am Samstag, 7. März 2026, 16:31:18 Mitteleuropäische Normalzeit schrieb Simon Josefsson:
> Morten Linderud <foxboron@archlinux.org> writes:
>
> > A lot of this is probably already a lost cause I think.
>
> +1
Here's another example of a (cryptography-related) package gone full auto.
https://github.com/cpan-authors/Crypt-OpenSSL-RSA/commits/main/?after=5d7e2e6faf3d6938b55aeebd40f5fb2379248c36+34
Lost cause or not, shouldnt we even try to fight this tendency?
I mean, it's one thing to vibe-code a sandboxed browser game where graphics glitches are
the worst possible outcome... but...
--
PD Dr. Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
next prev parent reply other threads:[~2026-03-22 23:53 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
2026-03-22 23:53 ` Andreas K. Huettel [this message]
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=2081671.zToM8qfIzz@noumea \
--to=dilfridge@gentoo.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.