unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: help-guix@gnu.org
Subject: Re: On network management and documenting nmcli
Date: Tue, 22 May 2018 14:42:19 +0200	[thread overview]
Message-ID: <1d86d711-8917-effc-c1e1-0fc09d23c5c8@riseup.net> (raw)
In-Reply-To: <87r2mfqs3j.fsf@gmail.com>

On 2018-05-13 21:21, Pierre Neidhardt wrote:
> You are very true, and while the manual hints at
> lightweight-desktop.scm, it does not go any further with respect to
> giving an outlook of what to expect from it: which services, which
> programs, etc.
>
> With little Scheme code the experienced users can investigate that by
> themselves, but it's not quite obvious for newcomers.
>
> If not only for nmcli, I would suggest we document more those
> pre-defined profiles for the sake of making GuixSD more approachable.
I agree.

Here we could choose between just listing them in the manual which 
increases the work on updating the manual when we change the default 
profiles or
Giving the newcomers the means to see for themselves what 
programs/services they contain. This should be done in a way that 
explains more than the name of the service/package does.

Perhaps a new guix command is needed for this e.g.:

% guix show %default-services

getty              | A service that serves tty

cups               | Printing service that enables printing

...
For information about how to remove or add services see Services (info) in the manual.

This command "guix show" could then be hinted at in the example 
configuration files.

---
Swedebugia

  reply	other threads:[~2018-05-22 15:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 10:02 On network management and documenting nmcli Pierre Neidhardt
2018-05-11 12:21 ` Oleg Pykhalov
2018-05-11 12:57   ` Devan Carpenter
2018-05-11 13:00     ` Pierre Neidhardt
2018-05-11 13:10       ` Devan Carpenter
2018-05-11 13:15         ` Pierre Neidhardt
2018-05-13  7:26         ` Nils Gillmann
2018-05-13 11:08           ` swedebugia
2018-05-13 12:22             ` Nils Gillmann
2018-05-13 12:33               ` Nils Gillmann
2018-05-13  2:31 ` Chris Marusich
2018-05-13  7:13   ` Pierre Neidhardt
2018-05-13 17:44     ` Chris Marusich
2018-05-13 19:21       ` Pierre Neidhardt
2018-05-22 12:42         ` swedebugia [this message]
2018-05-22 15:26           ` Pierre Neidhardt
2018-05-23 15:39           ` Ludovic Courtès
2018-05-23 15:45             ` Pierre Neidhardt
2018-05-23 18:18               ` swedebugia
2018-05-24 12:33               ` Ludovic Courtès
2018-05-24 12:40                 ` Pierre Neidhardt

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=1d86d711-8917-effc-c1e1-0fc09d23c5c8@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=help-guix@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.
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).