From: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
To: Paul van der Walt <paul@denknerd.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Website, differentiating GuixSD vs Guix
Date: Thu, 21 May 2015 16:43:15 -0500 [thread overview]
Message-ID: <af06da0041130707e58e555448827483@openmailbox.org> (raw)
In-Reply-To: <87d21vrr3q.fsf@denknerd.org>
On 2015-05-20 14:22, Paul van der Walt wrote:
> Hello Guix,
>
> Minor headache i had, thought i'd share.
>
> Went to the website to download the binary tarball (which seems to work
> very well, kudos!), but was bitten by the fact that the GuixSD and GNU
> Guix downloads aren't separated. I first ended up with GuixSD instead
> of
> Guix, then after reading way too quickly concluded that i686 was what i
> wanted, ended up with the wrong Guix for my platform (x86_64, which is
> visually at the end of the "list" containing GuixSD 0.8.2 (x86_64) and
> GuixSD 0.8.2 (i686)).
>
> So, i realise i should read more carefully and all, but perhaps a
> horizontal rule between the two GuixSD and the 4 GNU Guix downloads
> would be nice?
>
> Feel free to call me hasty and myopic or just ignore me. Otherwise it
> looks really polished, congrats :)
>
> Ciao,
> p.
Hey, Paul, thanks for your feedback.
The items in the download page will be updated to look like in the
following mock-up to make them more compact:
https://multimedialib.files.wordpress.com/2015/05/guixsd-downloads-mockup-2015-05-21.png
Hopefully, the new design will also help people who push buttons without
reading (just kidding :)).
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/
next prev parent reply other threads:[~2015-05-21 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 19:22 Website, differentiating GuixSD vs Guix Paul van der Walt
2015-05-21 21:43 ` Luis Felipe López Acevedo [this message]
2015-05-24 16:44 ` Amirouche Boubekki
2015-05-24 17:31 ` Luis Felipe López Acevedo
2015-05-25 14:18 ` Ludovic Courtès
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=af06da0041130707e58e555448827483@openmailbox.org \
--to=felipe.lopez@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=paul@denknerd.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.
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.