all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "\(" <paren@disroot.org>, 59822@debbugs.gnu.org
Subject: [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button.
Date: Mon, 05 Dec 2022 18:06:15 +0100	[thread overview]
Message-ID: <87edtdu6ew.fsf@pelzflorian.de> (raw)
In-Reply-To: <86tu2a444p.fsf@gmail.com> (zimoun's message of "Mon, 05 Dec 2022 10:00:06 +0100")

Hi all.

My reluctance is because there isn’t an advantage to using the latest image.

zimoun <zimon.toutoune@gmail.com> writes:
> this sentence could be added,
>
> These images are well-tested released images, and since Guix follows
> rolling release model, you might prefer to use [latest images](https://guix.gnu.org/en/download/latest/)

This is not a reason.  On the contrary, users of 1.3.0 will get the
current software once they upgrade.

I can think of one consequence of using the 1.3.0 image: Users might
have to adapt the generated config.scm once they pull and reconfigure.
For example, because of changes in the swap-space definition.  But this
isn’t really a downside, since the OS configuration is the reason to use
Guix on Guix System instead of a foreign distro.

There maybe is hardware that is not yet supported on standard installer
images.  But it doesn’t need to be mentioned.  There are no cutting edge
hardware users on a libre distro, are there?  Except those using tainted
versions of the installer, not offered here.

Lastly, I’m reluctant to change existing sentences, because they will
not be translated soon enough.

Am I mistaken?

Regards,
Florian




  reply	other threads:[~2022-12-05 17:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 19:50 [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button ( via Guix-patches via
2022-12-04 21:50 ` pelzflorian (Florian Pelz)
2022-12-04 21:58   ` pelzflorian (Florian Pelz)
2022-12-04 22:03     ` pelzflorian (Florian Pelz)
2022-12-05  7:02       ` ( via Guix-patches via
2022-12-05  8:00         ` pelzflorian (Florian Pelz)
2022-12-05  9:00           ` zimoun
2022-12-05 17:06             ` pelzflorian (Florian Pelz) [this message]
2022-12-05 17:41               ` pelzflorian (Florian Pelz)
2022-12-06 11:22               ` zimoun
2022-12-06 16:33                 ` pelzflorian (Florian Pelz)
2022-12-06 17:45                   ` zimoun
2022-12-07 14:26                     ` pelzflorian (Florian Pelz)
2022-12-08  9:36                       ` pelzflorian (Florian Pelz)
2022-12-08 10:12                         ` zimoun
2022-12-08 11:50                           ` bug#59822: " pelzflorian (Florian Pelz)
2022-12-08 15:49                             ` [bug#59822] " ( via Guix-patches via
2022-12-05 16:51           ` ( via Guix-patches via
2022-12-08 16:44             ` pelzflorian (Florian Pelz)
2022-12-08 16:46               ` ( via Guix-patches via
2022-12-08 18:10               ` zimoun
2022-12-08 19:44                 ` pelzflorian (Florian Pelz)
2022-12-21 13:40                 ` Ludovic Courtès
2022-12-30 12:21                   ` zimoun
2022-12-31 15:43                     ` pelzflorian (Florian Pelz)
2023-01-06 22:53                     ` Ludovic Courtès
2023-01-07  7:29                       ` pelzflorian (Florian Pelz)
2023-01-09 10:13                         ` Simon Tournier
2023-01-09 19:35                           ` pelzflorian (Florian Pelz)
2023-01-11 16:11                             ` Simon Tournier
2023-01-12 17:56                               ` pelzflorian (Florian Pelz)
2022-12-05  7:01   ` ( via Guix-patches via

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=87edtdu6ew.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=59822@debbugs.gnu.org \
    --cc=paren@disroot.org \
    --cc=zimon.toutoune@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 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.