From: Simon Tournier <zimon.toutoune@gmail.com>
To: Attila Lendvai <attila@lendvai.name>
Cc: jgart <jgart@dismail.de>, guix-devel@gnu.org
Subject: Re: more than 1,800 dependent packages: website out of date
Date: Tue, 26 Sep 2023 12:26:12 +0200 [thread overview]
Message-ID: <CAJ3okZ2gQak9XMNdF12JsZM3Xh0N8xU2VpeFTqi26y9f_YEPPQ@mail.gmail.com> (raw)
In-Reply-To: <-jSdhis7BbVfF8bnsiwhRyFhpCHiOtTFJoLQx3ksf9u6_CpIJ7JoVLUbUYG1mtwvc7YfbajoJx7GOna2jdaxq3BQRRsN6bHugJgehtn1pYg=@lendvai.name>
Hi,
On Tue, 26 Sept 2023 at 11:55, Attila Lendvai <attila@lendvai.name> wrote:
> > > When will the above website be updated to use the latest manual
> > > information about branches?
> >
> > What do you mean?
> >
> > 1. The manual you are pointing is the released v1.4.0 manual, not the
> > latest one. This v1.4.0 manual is set in stone and is a snapshot
> > of Guix at v1.4.0.
>
> if Guix is using a rolling release model, then maybe it's not an unreasonable expectation that the online manual also follows the latest in the git repo, no?
>
> maybe we should stop prefixing devel/, and start prefixing the releases?
Here is the website:
https://guix.gnu.org/
On the top, under Download, you have Standard vs Latest.
Under Help, you have "GNU Guix manual 1.4.0" vs "GNU Guix manual (latest)".
You are proposing that https://guix.gnu.org/en/manual/ points to the
latest manual.
That https://guix.gnu.org/en/manual/devel/ is removed or redirected to
https://guix.gnu.org/en/manual/.
And that https://guix.gnu.org/en/manual/v1.4.0 points to the frozen
manual of v1.4.0.
Right?
Please note that the manual of the last release (1.4.0) is kept around
only for people installing from released images before they run "guix
pull".
So maybe, we could remove "GNU Guix manual 1.4.0" from the Help
section and just mention it in the Download
(https://guix.gnu.org/en/download/) webpage.
Well, I do not know.
Cheers,
simon
next prev parent reply other threads:[~2023-09-26 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 3:18 more than 1,800 dependent packages: website out of date jgart
2023-09-26 5:32 ` Simon Tournier
2023-09-26 9:55 ` Attila Lendvai
2023-09-26 10:26 ` Simon Tournier [this message]
2023-09-26 16:39 ` Maxim Cournoyer
2023-09-26 16:42 ` jgart
2023-09-26 14:15 ` jgart
[not found] <mailman.14714.1695741617.1171.guix-devel@gnu.org>
2023-09-26 18:04 ` Peter Polidoro
2023-09-26 19:54 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 6:28 Nathan Dehnel
2023-09-28 6:35 ` Ricardo Wurmus
2023-09-28 14:11 ` Nathan Dehnel
2023-09-29 7:32 ` Simon Tournier
2023-10-04 15:33 ` Ludovic Courtès
2023-10-04 17:50 ` Simon Tournier
2023-10-14 16:11 ` Maxim Cournoyer
2023-10-18 17:55 ` Simon Tournier
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=CAJ3okZ2gQak9XMNdF12JsZM3Xh0N8xU2VpeFTqi26y9f_YEPPQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/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).