unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: George Clemmer <myglc2@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Clément Lassieur" <clement@lassieur.org>, 31786@debbugs.gnu.org
Subject: bug#31786: 'pre-inst-env guix --version' is not updated by new commits"
Date: Fri, 15 Jun 2018 21:35:29 -0400	[thread overview]
Message-ID: <87zhzvh5su.fsf@gmail.com> (raw)
In-Reply-To: <87po0r674z.fsf@elephly.net>


Ricardo Wurmus <rekado@elephly.net> writes:

> Hi George,
>
>> The current doc reflects the needs and sensibilities of the hackers,
>> maintainers, and sysops that have built Guix. These "elite" users have
>> different needs and judge what is important quite differently from end
>> users. This guarantees that the current doc is inadequate for end users.
>> So, if, as you say, you want to make Guix accessible to end users, you
>> need to make changes in the doc.  The questions: How? What?
> […]
>> I said: I use 'pre-inst-env guix' this way and this is a bug.
>
> “pre-inst-env” really should not be used by people other than
> developers.  It is only available when building Guix from a clone of the
> git repository.
>
> We do not recommend “pre-inst-env” for any other purpose than to make
> changes to the code, so I would not like to document the quirks and
> limitations of “pre-inst-env” in the manual, as this is not how Guix is
> supposed to be used generally.
>
>> Proposed (revised) footnote:
>>
>> (3) The Guix version in the Guix build is set by './bootstrap'. Thus,
>> the version reported by './pre-inst-env guix --version' is not updated
>> by subsequent 'git pull; make' steps. To update the version (and rebuild
>> everything), use 'git clean -dfx; ./bootstrap; ./configure; make'.
>
> I’m wary of adding this for similar reasons that Ludo wrote earlier.  In
> my opinion this ends up cluttering the manual with notes and what I
> consider to be only tangentially relevant for readers of the manual.

Hi Ricardo,

Please read further down the original post. I think you will find that I
already addressed your points.

Collectively, the responses here bring to mind a Harvard Business School
case study I was taught in 1983. The gist of it: Bakers at Holsum Bread
told a salesman that they had figured out how to run his company's bread
making machine at twice the design speed. Because this was twice as fast
as the competitor's machine, they wanted to place a big order for more
machines. When the salesman told the company engineer about the order he
said, "You can't sell any more machines to Holsum because they aren't
using my machine properly!"

- George

      parent reply	other threads:[~2018-06-16  1:36 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
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 [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

  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=87zhzvh5su.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=31786@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=rekado@elephly.net \
    /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).