From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Mekeor Melire <mekeor@posteo.de>, guix-devel@gnu.org
Subject: Re: Split (gnu packages suckless) module
Date: Fri, 29 Oct 2021 06:22:28 +0200 [thread overview]
Message-ID: <f448998fe118cc02d1f053a25df078ef0c943310.camel@gmail.com> (raw)
In-Reply-To: <875ythox5i.fsf@posteo.de>
Hi Guix,
Am Donnerstag, den 28.10.2021, 15:55 +0000 schrieb Mekeor Melire:
> The reasons for this proposal are:
>
> 1. We generally do not create modules according to the groups of
> developers, but rather package declarations are grouped into
> modules according to their function (e.g. "wm") or according to
> some technical or factual realm they belong to (e.g. "haskell"
> or "music"). There is no reason why software from the Suckless
> group should not follow this rule.
Actually, the software from the suckless group follows this rule in a
sense, as we also have a module for freedesktop, gnome, kde, etc.
> 2. There are hints indicating that the Suckless group sympathizes
> to oppressive Nazi ideology. The Suckless group is a registered
> association in Munich, Germany.
This is a somewhat weak argument, as filenames only matter when editing
– you'd still be linking to a Nazi group in the homepage, which matters
much more.
On the other hand, Guix users often complain about suckless-style
software as it is in fact not the most Guix-friendly to handle. Simply
renaming the file to "suckmore" would in my opinion be adequate, and
switching to maintained forks of their stuff ethical.
Regards,
Liliana
next prev parent reply other threads:[~2021-10-29 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 15:55 Split (gnu packages suckless) module Mekeor Melire
2021-10-29 3:20 ` Leo Famulari
2021-10-29 15:19 ` Ludovic Courtès
2021-10-29 4:22 ` Liliana Marie Prikler [this message]
2021-10-29 16:45 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f448998fe118cc02d1f053a25df078ef0c943310.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mekeor@posteo.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).