From: Leo Famulari <leo@famulari.name>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Mekeor Melire <mekeor@posteo.de>, guix-devel@gnu.org
Subject: Re: Split (gnu packages suckless) module
Date: Fri, 29 Oct 2021 12:45:31 -0400 [thread overview]
Message-ID: <YXwlK0uVOLVxcyoK@jasmine.lan> (raw)
In-Reply-To: <f448998fe118cc02d1f053a25df078ef0c943310.camel@gmail.com>
On Fri, Oct 29, 2021 at 06:22:28AM +0200, Liliana Marie Prikler wrote:
> Am Donnerstag, den 28.10.2021, 15:55 +0000 schrieb Mekeor Melire:
> > 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.
I think there is a distinction with these groups compared to suckless.
These software written by these groups is tightly coupled, relying on
shared libraries and APIs. They intend to create a cohesive and
integrated operating system.
Whereas the suckless software does not share code or APIs, at least as I
understand it, and does not seek to create a cohesive OS beyond the
classic loosely coupled "Unix" idea.
prev parent reply other threads:[~2021-10-29 17:19 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
2021-10-29 16:45 ` Leo Famulari [this message]
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=YXwlK0uVOLVxcyoK@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--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).