From: zimoun <zimon.toutoune@gmail.com>
To: "George Clemmer" <myglc2@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>,
elaexuotee@wilsonb.com
Cc: guix-devel@gnu.org
Subject: Re: Using --manfistest with <profile>/manifest files
Date: Tue, 16 Jun 2020 11:38:03 +0200 [thread overview]
Message-ID: <86blljs64k.fsf@gmail.com> (raw)
In-Reply-To: <85ftav206f.fsf@gmail.com>
Dear,
On Mon, 15 Jun 2020 at 22:51, George Clemmer <myglc2@gmail.com> wrote:
> ISTM we set ourselves up for confused users and a lot of explaining by
> labeling two very different things with same name :-0
I think there is a confusion here. The file <profile>/manifest is an
internal detail implementation and the user should *not* be exposed to.
Well, there are a lot of internal files that the user is not aware. And
sometimes, the names are more or less well-chosen. But hey! it is
internal and naming is hard. :-)
> Yes, only 'manifest.scm' is in the doc, but '.guix-profile/manifest'
> smacks a user in the face pretty quickly which leads to these messy
> questions.
I am not convinced by "smacks in the face pretty quickly". But I agree
that questions about this topic regularly come. For example, to pick an
old one:
https://lists.gnu.org/archive/html/guix-devel/2018-10/msg00011.htlm
> IMO we could dramatically simplify the situation, and simplify our
> lives, by simply renaming the .guix-profile/manifest file ;-)
In contradiction with what I wrote above, I agree. :-)
<profile>/manifest should be renamed <profile>/specifications or
something like that.
And a comment could be inserted in this file saying: internal usage, do
not modify, etc..
WDYT?
All the best,
simon
next prev parent reply other threads:[~2020-06-16 9:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 1:40 Using --manfistest with <profile>/manifest files elaexuotee
2020-06-13 20:36 ` Ludovic Courtès
2020-06-14 10:17 ` Pierre Neidhardt
2020-06-14 15:24 ` Ludovic Courtès
2020-06-15 7:52 ` Pierre Neidhardt
2020-06-16 9:44 ` Ludovic Courtès
2020-06-15 8:08 ` zimoun
2020-06-16 9:46 ` Ludovic Courtès
2020-06-16 11:33 ` elaexuotee
2020-06-16 13:42 ` zimoun
2020-06-17 0:45 ` elaexuotee
2020-06-17 7:58 ` how to "guix pack" a profile? zimoun
2020-06-18 9:20 ` elaexuotee
2020-06-18 23:49 ` zimoun
2020-06-19 2:52 ` elaexuotee
2020-06-19 8:30 ` zimoun
2020-06-19 12:34 ` elaexuotee
2020-06-19 15:38 ` zimoun
2020-06-19 10:00 ` zimoun
2020-06-19 12:16 ` elaexuotee
2020-06-19 20:40 ` Ludovic Courtès
2020-06-19 20:35 ` Ludovic Courtès
2020-06-16 2:51 ` Using --manfistest with <profile>/manifest files George Clemmer
2020-06-16 4:27 ` elaexuotee
2020-06-17 19:09 ` George Clemmer
2020-06-16 9:38 ` zimoun [this message]
2020-06-16 14:03 ` George Clemmer
2020-06-16 15:09 ` zimoun
2020-06-16 9:50 ` Ludovic Courtès
2020-06-15 7:54 ` zimoun
2020-06-15 10:08 ` elaexuotee
2020-06-16 9:09 ` zimoun
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=86blljs64k.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=elaexuotee@wilsonb.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=myglc2@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 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).