all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: Ludovic Court??s <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [shepherd] herd status suggestion
Date: Sun, 10 Jun 2018 19:47:57 +0000	[thread overview]
Message-ID: <20180610194757.v5io5whztrxbxdpt@abyayala> (raw)
In-Reply-To: <874liae8iu.fsf@gnu.org>

Ludovic Court??s transcribed 1.3K bytes:
> Hello Nils,
> 
> Nils Gillmann <ng0@n0.is> skribis:
> 
> > Ricardo Wurmus transcribed 982 bytes:
> >> 
> >> Hi Nils,
> >> 
> >> > abyayala$ sudo herd status tor
> >> > Status of tor:
> >> >   It is stopped.
> >> >   It is disabled.
> >> >   Provides (tor).
> >> >   Requires (user-processes loopback syslogd).
> >> >   Conflicts with ().
> >> >   Will be respawned.
> >> >   Last respawned on Sun Jun 10 08:08:45Z 2018.
> >> >
> >> >
> >> > Would it be an option to change the status output to,
> >> > if it conflicts with no other service:
> >> >
> >> >   Conflicts with no other services.
> >> >
> >> > instead of the representation of an empty list?
> 
> [...]
> 
> > Related and similar: Would it be reasonable to change the output from list-style,
> > like:
> >   Depends on: (foo bar irks boot)
> >
> > to the probably tiny bit better readable:
> >
> >   Depends on: foo, bar, irks, boot
> >
> > for humans?
> 
> I agree with both proposals.  :-)
> 
> The output of ‘herd status’ is meant for humans to read, not for
> machines to process, so it makes sense to make these changes IMO.  For
> machines there’s a well-defined protocol that can be used, so we should
> do our best to make ‘herd status’ useful to humans.
> 
> If you want to give it a try, this is all happening in
> modules/shepherd/scripts/herd.scm.
> 
> Thank you,
> Ludo’.
> 

Thanks!

I will see when I find the time. If I can't work on this in time, I'll let you know.

      reply	other threads:[~2018-06-10 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-10 10:34 [shepherd] herd status suggestion Nils Gillmann
2018-06-10 11:31 ` Ricardo Wurmus
2018-06-10 14:31   ` Nils Gillmann
2018-06-10 19:39     ` Ludovic Courtès
2018-06-10 19:47       ` Nils Gillmann [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180610194757.v5io5whztrxbxdpt@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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.