unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Leo Prikler <leo.prikler@student.tugraz.at>,
	48924@debbugs.gnu.org, efraim@flashner.co.il, Tony O <me@fron.io>
Subject: [bug#48924] Add systemd
Date: Mon, 14 Jun 2021 11:25:09 -0400	[thread overview]
Message-ID: <YMd01e33raUWNh9P@jasmine.lan> (raw)
In-Reply-To: <877diwy6gd.fsf@gnu.org>

On Mon, Jun 14, 2021 at 02:30:10PM +0200, Ludovic Courtès wrote:
> No no, I was careful to apply the same standards.  :-)  My main
> question is whether it’s usable at all:
> 
>   https://issues.guix.gnu.org/48924#1
> 
> Tony’s use case has to do with satisfying the dependencies of a
> binary-only proprietary executable:
> 
>   https://issues.guix.gnu.org/48924#2
> 
> To me, that use case alone isn’t enough to justify maintaining systemd
> in Guix proper.

It's true, that's not really a good reason to add the package. There are
probably some existing Guix packages with a similar use case, but nobody
ever said it out loud. It's a lesson in the value of discretion, I
suppose.

> However, if, as Efraim suggests, a systemd package has some uses, at
> least on foreign distros, then that’s fine with me.  It’s a very narrow
> use case (running ‘loginctl’ on a foreign distro), but why not.
> 
> Thoughts?

To me, it's a simple scenario: We received a contribution to add a
popular free software program.

But it has been complicated by the broader context, about which I
already shared my uncharitable interpretation, and that's a shame. Now
there is a big discussion about it.

I would add the package. We should feel free to remove packages
(especially leaf packages) that aren't building or are far behind the
upstream release schedule if nobody is trying to fix them. We don't have
to assume a burden of maintenance.




  reply	other threads:[~2021-06-14 15:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 16:19 [bug#48924] Add systemd Tony O
2021-06-09 17:42 ` Ludovic Courtès
2021-06-09 18:08   ` Tony O
2021-06-09 20:25     ` Ludovic Courtès
2021-06-09 20:31       ` Tony O
2021-06-09 22:33         ` Leo Prikler
2021-06-11 16:39           ` Ludovic Courtès
2021-06-11 17:11             ` Leo Prikler
2021-06-13  7:31               ` Efraim Flashner
2021-06-13  9:36                 ` Ludovic Courtès
2021-06-13 12:19                   ` Efraim Flashner
2021-06-13 18:14                   ` Leo Famulari
2021-06-13 18:54                     ` Tony O
2021-06-13 19:00                       ` Leo Prikler
2021-06-13 19:56                         ` Tony O
2021-06-13 21:44                           ` Leo Prikler
2021-06-13 22:35                             ` Leo Famulari
2021-06-14 12:30                               ` Ludovic Courtès
2021-06-14 15:25                                 ` Leo Famulari [this message]
2021-06-15  9:38                                   ` Ludovic Courtès
2021-06-15 13:40                                     ` Leo Famulari
2021-06-15  6:35                                 ` Efraim Flashner
2021-06-15  9:29                                   ` Ludovic Courtès

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=YMd01e33raUWNh9P@jasmine.lan \
    --to=leo@famulari.name \
    --cc=48924@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=leo.prikler@student.tugraz.at \
    --cc=ludo@gnu.org \
    --cc=me@fron.io \
    /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).