unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>, 53224 <53224@debbugs.gnu.org>
Subject: Re: Profile definition, was Re: bug#53224: Cookbook recipe about profile collisions
Date: Mon, 17 Jan 2022 13:40:53 -0500	[thread overview]
Message-ID: <YeW4NTPzi9LQt+4E@jasmine.lan> (raw)
In-Reply-To: <17e692ec987.c9fc5e4191836.2115614241637446332@excalamus.com>

On Mon, Jan 17, 2022 at 12:56:20PM -0500, Matt wrote:
> Leo is 100% correct that my understanding is still rather weak. I'll do my best despite that to help make the documentation better.

I hope you will not feel too bad about that. Remember, everyone begins
by not knowing anything. Your situation is not unique at all. Rather,
your energy for improving the documentation for yourself and others is
exemplary, and will improve Guix in the long run.

Overall, this highlights a case where there is tension between when an
implementation detail doesn't matter, and when it does. That is, the
ideal situation is that the implementation details of profiles do not
matter. However, when there are "profile collisions", it does matter.


  reply	other threads:[~2022-01-17 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Yd9uT579+YLI5HIx@jasmine.lan>
     [not found] ` <87v8ym4sav.fsf@gnu.org>
     [not found]   ` <YeHCZgO5c+I36Flr@jasmine.lan>
     [not found]     ` <87pmoqo3b7.fsf@gnu.org>
2022-01-17 17:56       ` Profile definition, was Re: bug#53224: Cookbook recipe about profile collisions Matt
2022-01-17 18:40         ` Leo Famulari [this message]
2022-01-18 15:36           ` Ludovic Courtès
2022-01-19  2:41             ` Matt

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=YeW4NTPzi9LQt+4E@jasmine.lan \
    --to=leo@famulari.name \
    --cc=53224@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=matt@excalamus.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 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).