unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Remco van 't Veer <remco@remworks.net>
To: Sergiu Ivanov <sivanov@colimite.fr>
Cc: help-guix@gnu.org
Subject: Re: Examples of local-host-entries or hosts-service-type?
Date: Tue, 14 Feb 2023 10:34:57 +0100	[thread overview]
Message-ID: <87fsb8si7y.fsf@remworks.net> (raw)
In-Reply-To: <87k00ltxgs.fsf@colimite.fr>

Hi Sergiu,

2023/02/13 11:49, Sergiu Ivanov:

> Actually, where did you get local-host-entries from?  The documentation
> page you and Bruno cite doesn't seem to ever mention this function :O
> Unless I am looking at some old version of the docs.

To be honest, I did not know about local-host-entries before your email
and thought it would allow me to cleanup my own (operating-system
.. (hosts-file (plain-file .. (string-append ..) mess.  So I did some
digging in the guix source and found some references in gnu/system.scm.

>> Also, I agree the documentation needs some love here.
>
> I am willing to contribute.  What would be the best place to do changes
> to the documentation?

doc/guix.texi

> I would follow this mini-roadmap:
>
> 1. Add the explanation of local-host-entries to
>    https://guix.gnu.org/en/manual/devel/en/html_node/Service-Reference.html#index-hosts_002dservice_002dtype
>
> 2. Say here
>    https://guix.gnu.org/manual/en/html_node/operating_002dsystem-Reference.html
>    that hosts-file is deprecated.
>
> 3. Update the examples here to use hosts-service-type instead of
>    hosts-file: https://guix.gnu.org/manual/en/guix.html
>
> What do you think?

Sounds like a plan to me.  Note: all the above is part of doc/guix.texi,
I think.

> I've never submitted a patch to Guix docs before, so all suggestions and
> hints are welcome :-)

Me neither (apart from a typo I found in the Service Reference section
during grepping for examples).  I don't have a clue about how
translations are kept in sync.  Maybe just go for it and collect some
feedback with a patch.

Cheers,
Remco


  reply	other threads:[~2023-02-14  9:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 22:40 Examples of local-host-entries or hosts-service-type? Sergiu Ivanov
2023-02-10 23:37 ` Bruno Victal
2023-02-11 11:46 ` Remco van 't Veer
2023-02-13 10:49   ` Sergiu Ivanov
2023-02-14  9:34     ` Remco van 't Veer [this message]
2023-02-21 15:33   ` Gary Johnson
2023-02-26 18:33     ` Sergiu Ivanov
2023-02-21 16:45   ` Bruno Victal
2023-02-26 18:05     ` Sergiu Ivanov
2023-02-27  6:23     ` Remco van 't Veer
2023-03-02  2:41       ` Bruno Victal
2023-03-02  8:47         ` Remco van 't Veer
2023-03-03 14:00           ` Bruno Victal
2023-03-03 16:16             ` Remco van 't Veer

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=87fsb8si7y.fsf@remworks.net \
    --to=remco@remworks.net \
    --cc=help-guix@gnu.org \
    --cc=sivanov@colimite.fr \
    /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).