unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: George Clemmer <myglc2@gmail.com>
Cc: 31786@debbugs.gnu.org
Subject: bug#31786: 'pre-inst-env guix --version' is not updated by new commits"
Date: Thu, 14 Jun 2018 18:36:31 +0200	[thread overview]
Message-ID: <87k1r1z5o0.fsf@gnu.org> (raw)
In-Reply-To: <87d0wttn0v.fsf@gmail.com> (George Clemmer's message of "Thu, 14 Jun 2018 11:18:08 -0400")

Hi George,

George Clemmer <myglc2@gmail.com> skribis:

> Leo Famulari <leo@famulari.name> writes:
>
>> On Wed, Jun 13, 2018 at 08:54:49AM +0200, Ludovic Courtès wrote:
>>> The other aspect, from a maintenance and readability viewpoint, is that
>>> we could quickly add up lots of explanations that we’ll have to keep
>>> up-to-date and that may make more important information harder to find.
>>
>> Yeah, I'm worried about this too. It's tough to strike the correct
>> balance.
>
> IMO Guix is great for hackers, maintainers and sysops. The doc is
> appropriate for such users, well done, spare, and already voluminous.
>
> This footnote suggestion, and others rejected in the past, are motivated
> by my assumption that you will want to make Guix attractive to less
> sophisticated users.
>
> Maybe my assumption is wrong? Maybe you want only "elite" users?

No, definitely not; I’m sorry if this is the impression this gave.

Like I wrote, my main concern is about keeping the documentation focused
and maintainable.  Sometimes we have to document things that are
technically outside of Guix because there’s no real canonical
documentation and because users would be impaired without it—I’m
thinking for instance of bits in the “Preparing for Installation”
section.

In this case, we’d be documenting something that’s both outside of Guix
and not vital for routine usage, and that’s mostly covered by the
Autoconf manual.  Hence my reluctance.

I hope that makes sense.

Ludo’.

  parent reply	other threads:[~2018-06-14 16:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 18:01 bug#31786: 'pre-inst-env guix --version' is not updated by new commits" George Clemmer
2018-06-12 13:21 ` Ludovic Courtès
2018-06-12 18:28   ` George Clemmer
2018-06-12 20:33     ` Ludovic Courtès
2018-06-13  0:51       ` George Clemmer
2018-06-13  6:54         ` Ludovic Courtès
2018-06-14  1:39           ` Leo Famulari
2018-06-14 15:18             ` George Clemmer
2018-06-14 16:10               ` Clément Lassieur
2018-06-14 16:45                 ` Clément Lassieur
2018-06-14 16:36               ` Ludovic Courtès [this message]
2018-06-15 19:13                 ` George Clemmer
2018-06-15 20:30                   ` Nils Gillmann
2018-06-16 16:06                     ` George Clemmer
2018-06-15 22:02                   ` Ricardo Wurmus
2018-06-15 22:24                     ` Ricardo Wurmus
2018-06-19 16:47                       ` myglc2
2018-06-16  1:35                     ` George Clemmer

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=87k1r1z5o0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31786@debbugs.gnu.org \
    --cc=myglc2@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).