From: Pierre Neidhardt <mail@ambrevar.xyz>
To: guix-devel@gnu.org
Subject: Store channel specification in profile
Date: Tue, 26 Nov 2019 15:55:21 +0100 [thread overview]
Message-ID: <87blsyelgm.fsf@ambrevar.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
Hi,
After the long discussions we had on profile, guix environment,
manifest, multi-dimensional rollbacks, etc. I suggest the following fix:
let's store the "channel specifications" in the profile / environment,
similar to how we store the manifest in etc/manifest.
What I call "channel specification" is essentially the output of `guix
describe -f channels`. Unless some official term already exists, I
propose to document this term in the manual.
I propose to store the channel spec under
"etc/channel-specification.scm".
Or shall we opt for the shorter "etc/channl-spec"?
One question arises though: channel specifications only make sense for
profiles generated with manifests. What about ad-hoc profiles? Shall
we still store the spec in this case? I propose we don't, this could
also be a hacky way to check whether a profile is ad-hoc or not.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2019-11-26 15:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 14:55 Pierre Neidhardt [this message]
2019-11-26 16:40 ` Store channel specification in profile Konrad Hinsen
2019-11-26 19:12 ` Pierre Neidhardt
2019-11-26 19:35 ` Konrad Hinsen
2019-12-02 15:58 ` zimoun
2019-12-09 17:11 ` Ludovic Courtès
2019-12-09 17:21 ` Pierre Neidhardt
2019-12-12 19:50 ` zimoun
2019-12-12 22:35 ` Pierre Neidhardt
2019-12-13 12:16 ` zimoun
2019-12-19 16:12 ` Ludovic Courtès
2019-12-19 17:18 ` zimoun
2020-01-06 20:07 ` Pierre Neidhardt
2020-01-06 21:09 ` zimoun
2020-01-08 15:17 ` Pierre Neidhardt
2020-01-08 19:31 ` zimoun
2020-01-11 23:48 ` Ludovic Courtès
2020-01-13 14:02 ` Pierre Neidhardt
2020-01-13 14:46 ` zimoun
2020-01-13 14:37 ` zimoun
2020-01-13 14:59 ` Pierre Neidhardt
2020-01-13 15:53 ` zimoun
2020-01-13 16:53 ` Pierre Neidhardt
2020-01-30 19:24 ` Pierre Neidhardt
2020-01-31 8:51 ` zimoun
2020-01-31 9:21 ` Konrad Hinsen
2020-01-31 11:21 ` Pierre Neidhardt
2020-01-31 12:15 ` Pierre Neidhardt
2020-01-31 16:01 ` Konrad Hinsen
2020-02-05 11:08 ` Ludovic Courtès
2020-02-06 10:59 ` Pierre Neidhardt
2020-02-07 21:28 ` Ludovic Courtès
2020-02-08 17:09 ` Pierre Neidhardt
2020-02-11 14:10 ` Ludovic Courtès
2020-02-11 14:18 ` Pierre Neidhardt
2020-02-24 16:16 ` Ludovic Courtès
2020-02-25 10:32 ` Pierre Neidhardt
2020-03-03 21:43 ` zimoun
2020-03-04 8:09 ` Pierre Neidhardt
2020-03-04 13:24 ` zimoun
2020-03-03 21:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blsyelgm.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.