all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 41565@debbugs.gnu.org
Subject: [bug#41565] [PATCH] doc: Use existing URLs and file names in installation instructions.
Date: Wed, 27 May 2020 13:17:30 -0400	[thread overview]
Message-ID: <20200527171730.GC28889@jasmine.lan> (raw)
In-Reply-To: <20200527173013.36a11a54@tachikoma.lepiller.eu>

On Wed, May 27, 2020 at 05:30:13PM +0200, Julien Lepiller wrote:
> Some users seem to be confused by the fact that our URLs in the manual
> don't work for them.  This is most likely because they copy them
> without reading the rest of the text which clearly says they should
> replace @var{system} with one of the supported values.  One example of
> this confusion is this conversation:
> https://mastodon.social/@Nixfreak/104224784493287104
> 
> Since our current approach doesn't seem to be very effective, I propose
> to change the URLs and file names with actual ones, using x86_64-linux
> as the system because this is the most popular platform that we support
> nowadays.  I keep mentioning the other architectures as alternatives,
> hoping that users will notice the x86_64 in the URL and keep reading to
> learn how to install Guix for another architecture if they want to.

I agree, it's a common mistake for new users. Your patch seems like the
right thing to do...




  parent reply	other threads:[~2020-05-27 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 15:30 [bug#41565] [PATCH] doc: Use existing URLs and file names in installation instructions Julien Lepiller
2020-05-27 15:50 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-27 17:17 ` Leo Famulari [this message]
2020-05-27 20:44 ` Marius Bakke
2020-05-27 21:29   ` bug#41565: " Julien Lepiller

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=20200527171730.GC28889@jasmine.lan \
    --to=leo@famulari.name \
    --cc=41565@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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.