unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 66577@debbugs.gnu.org
Subject: [bug#66577] [PATCH 0/4] Newcomer-oriented improvements to the manual and cookbook
Date: Tue, 17 Oct 2023 12:05:58 +0200	[thread overview]
Message-ID: <87il75mum1.fsf@gnu.org> (raw)
In-Reply-To: <cover.1697459606.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Mon, 16 Oct 2023 14:36:28 +0200")


Hello,

> regarding the section on multiple profiles in the cookbook (I’ve seen
> newcomers attempt to adopt that software management style on their
> systems, when it’s complex and in fact largely unnecessary since the
> addition of a fast cache in ‘guix shell’).

It is clear that "guix shell" is now an easier alternative to manual
profile management. So that commit:

>
>   doc: cookbook: Suggest ‘guix shell’ as an alternative to multiple
>     profiles.

and the rest of the series looks good to me.

Thanks,

Mathieu




  parent reply	other threads:[~2023-10-17 10:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 12:36 [bug#66577] [PATCH 0/4] Newcomer-oriented improvements to the manual and cookbook Ludovic Courtès
2023-10-16 12:43 ` [bug#66577] [PATCH 1/4] doc: Move “System Troubleshooting Tips” below Ludovic Courtès
2023-10-16 12:43 ` [bug#66577] [PATCH 2/4] doc: Mention Guix Home in “Getting Started” Ludovic Courtès
2023-10-18 16:19   ` Simon Tournier
2023-10-24 13:53     ` Ludovic Courtès
2023-10-16 12:43 ` [bug#66577] [PATCH 3/4] doc: cookbook: Suggest ‘guix shell’ as an alternative to multiple profiles Ludovic Courtès
2023-10-16 12:43 ` [bug#66577] [PATCH 4/4] doc: cookbook: Add cross references to the manual regarding manifests Ludovic Courtès
2023-10-17 10:05 ` Mathieu Othacehe [this message]
2023-10-18 16:34 ` [bug#66577] [PATCH 0/4] Newcomer-oriented improvements to the manual and cookbook Simon Tournier
2023-10-24 16:12   ` bug#66577: " 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

  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=87il75mum1.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=66577@debbugs.gnu.org \
    --cc=ludo@gnu.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 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).