From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Store channel specification in profile
Date: Mon, 6 Jan 2020 22:09:26 +0100 [thread overview]
Message-ID: <CAJ3okZ0GGJAJ_YRSdm4we-YYwUTzi85RvJkMHnPkSzVjVxPWSw@mail.gmail.com> (raw)
In-Reply-To: <874kx8gxh1.fsf@ambrevar.xyz>
Hi Pierre,
On Mon, 6 Jan 2020 at 21:07, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>
> zimoun <zimon.toutoune@gmail.com> writes:
>
> >> > Like zimoun writes, it would be nice to have some sort of a “describe”
> >> > command for a regular profile. Actually maybe “guix describe -p”?
> >> >
> >> > Actually ‘guix describe -p ~/.guix-profile’ works but doesn’t display
> >> > anything useful. We could fix that by recognizing the kind of profile,
> >> > somehow.
> >>
> >> Seems like a good idea. How do we define "anything useful" though?
> >> The provenance of packages? How would we format it?
You asked 3 questions. :-)
1. How do we define "anything useful" though?
2. The provenance of packages?
3. How would we format it?
And the answer of these 3 questions is the file <your-profile>/manifest.
> > As I explained elsewhere, the file <your-profile>/manifest already
> > contains almost all the information we need (at least I think we need
> > ;-)). But its format is not complaint with the other format (channels,
> > manifest). And you answered: it is plumbing! :-)
> > My point is: this plumbing manifest file should be more
> > "format-friendly" -- still being plumbing -- and easily compliant with
> > the --channel or --manifest option, IMHO.
>
> I agree. But changing the format might break compatibility with existing
> functions that rely on it. In which places are manifests used?
IMHO, the improvement of ‘guix describe -p ~/.guix-profile’ or even a
kind of profile manager (e.g., a new "guix profile" subcommand doing
pieces of "guix package" and/or maybe "guix environment") should use
this file <your-profile>/manifest. Therefore, there 3 directions, the
2 as you said:
a. keep the file <your-profile>/manifest as it is today; and add
options to convert it to regular manifests and channels.
b. improve the format of this file to obtain consistent manifests.
and c. improve what the --manifest option accepts.
At the user level, the option a. breaks nothing. This file
<your-profile>/manifest is not known -- I even do not know if it is
documented -- so the option b. might not break compatibility. About
functions that rely on it, I have not checked yet. And the option c.
needs to be discussed.
From my perspective, the option b. is a better path because it remove
layers and complexity.
> Should we not change the format, should we add a command line option to
> convert manifest to "manifest specifications" (those that work with
> `-manifest')? How do we include the provenance in manifest specifications?
The provenance of what?
Basically an entry looks like:
--8<---------------cut here---------------start------------->8---
("diffoscope"
"131"
"out"
"/gnu/store/h8zr4rxhvpikv9p07kdjkf2dsrja35wm-diffoscope-131"
(propagated-inputs ())
(search-paths ())
(properties
(provenance
(repository
(version 0)
(url "https://git.savannah.gnu.org/git/guix.git")
(branch "master")
(commit
"b5d4d5b9bcf267fddd02fcc14b88eac0bebf979f")))))
--8<---------------cut here---------------end--------------->8---
Cheers,
simon
next prev parent reply other threads:[~2020-01-06 21:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 14:55 Store channel specification in profile Pierre Neidhardt
2019-11-26 16:40 ` 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 [this message]
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=CAJ3okZ0GGJAJ_YRSdm4we-YYwUTzi85RvJkMHnPkSzVjVxPWSw@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.