all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 48924@debbugs.gnu.org, Tony O <me@fron.io>
Subject: [bug#48924] Add systemd
Date: Fri, 11 Jun 2021 19:11:18 +0200	[thread overview]
Message-ID: <6bb174687e5520154f4cb0fefe8306158d594c01.camel@student.tugraz.at> (raw)
In-Reply-To: <87h7i45p9y.fsf@gnu.org>

Hi,

Am Freitag, den 11.06.2021, 18:39 +0200 schrieb Ludovic Courtès:
> > 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.
I'm definitely leaning towards not including it as-is/perhaps having it
in an external channel as well, but I don't think "high maintenance"
should generally be a deterrent against a functioning package (or
rather the only reason to keep a package from being included).  Guix
already has packages, that I would consider to be of higher
maintenance, e.g. GNOME, and I do think it would help Guix users if
(parts of) systemd became a viable option.  I am simply doubting the
functionality of this package as it currently exists.

That said, I don't think myself to be in a place to make accurate
judgements about entry requirements.  I suggested “should be usable” as
a bare minimum because it seemed easy to convey.  There are also other
things to consider, like coding style, adherence to packaging
guidelines, etc. with maintainability somewhere among them, but I can't
really phrase all of those well into a simple sentence.  I also think
that some reviewer should be able to take an already functioning
package description and perform cosmetic changes to transform it into
one better suited for Guix, though that might be a bit of a
controversial statement.

Regards,
Leo






  reply	other threads:[~2021-06-11 17:12 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 [this message]
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=6bb174687e5520154f4cb0fefe8306158d594c01.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=48924@debbugs.gnu.org \
    --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 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.