From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 48924@debbugs.gnu.org, Tony O <me@fron.io>
Subject: [bug#48924] Add systemd
Date: Fri, 11 Jun 2021 18:39:37 +0200 [thread overview]
Message-ID: <87h7i45p9y.fsf@gnu.org> (raw)
In-Reply-To: <8c9f7f3961274fd2fef3b715a0ff8b21026bb283.camel@student.tugraz.at> (Leo Prikler's message of "Thu, 10 Jun 2021 00:33:03 +0200")
Hi,
Leo Prikler <leo.prikler@student.tugraz.at> skribis:
> Am Mittwoch, den 09.06.2021, 20:31 +0000 schrieb Tony O:
>> In particular, im using it to relink against a nonfree binary which
>> responds badly to tampering, so im using it only as a library.
> A systemd package, which serves no purpose other than being linked
> against nonfree binaries does not sound particularly useful, especially
> not when thinking in terms of FSDG compliance. We don't even know
> whether *free* software linked against this systemd would behave as
> expected, let alone nonfree software.
Yeah, that’s definitely not a good reason to include it.
> This was in part already discussed in IRC, but to reiterate, I think
> that the systemd package should be usable in some capacity -- be it,
> that we can run systemd as user daemons or be it, that we can
> *meaningfully* link free software against it. Note however, that the
> latter most likely implies the first, since there's no meaningful
> linkage against systemd without one of its daemons running.
Given the maintenance cost, we’d need a more convincing argument than
“should be usable”. :-)
So it seems to me that we’re done with it as far as inclusion in Guix is
concerned. Thoughts?
It’s typically a situation where an external channel is more
appropriate, IMO.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-06-11 16:40 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7i45p9y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48924@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.