unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, 66577@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#66577] [PATCH 2/4] doc: Mention Guix Home in “Getting Started”.
Date: Wed, 18 Oct 2023 18:19:23 +0200	[thread overview]
Message-ID: <87cyxbq4xg.fsf@gmail.com> (raw)
In-Reply-To: <2de53646c5355b42fec247780399fccb7c6a4f38.1697459606.git.ludo@gnu.org>

Hi Ludo,


On Mon, 16 Oct 2023 at 14:43, Ludovic Courtès <ludo@gnu.org> wrote:

>  @quotation Going further
>  @xref{Package Management}, for more about package management.  You may
>  like @dfn{declarative} package management with @command{guix package
> ---manifest}, managing separate @dfn{profiles} with @option{--profile},
> +--manifest},
>  deleting old generations, collecting garbage, and other nifty features
>  that will come in handy as you become more familiar with Guix.  If you
>  are a developer, @pxref{Development} for additional tools.  And if
>  you're curious, @pxref{Features}, to peek under the hood.

It is part of “Going further”, so I would let « managing separate
@dfn{profiles} with @option{--profile} ».  For what it is worth, I
recommend for some newcomer to still use a separated profile inside the
project folder, just aside the files manifest.scm and channels.scm.

I agree that “guix shell” is really cool now, but all the balance is the
duration of the project with the cache cleanup.

Well, this mention does not bother, IMHO, and it invites to know more
for the interested reader since it is “Going further”…

> +You can also manage the configuration of your entire @dfn{home
> +environment}---your user ``dot files'', services, and packages---using
> +Guix Home.  @xref{Home Configuration}, to learn more about it!
>  @end quotation

…I mean, similarly, Guix Home is not something I recommend for
newcomers.  But it is good to mention it in “Going further”. :-)


Cheers,
simon




  reply	other threads:[~2023-10-18 17:55 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 [this message]
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 ` [bug#66577] [PATCH 0/4] Newcomer-oriented improvements to the manual and cookbook Mathieu Othacehe
2023-10-18 16:34 ` 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=87cyxbq4xg.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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).