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: Tue, 3 Mar 2020 22:43:46 +0100 [thread overview]
Message-ID: <CAJ3okZ0s0GY66oQ+Cr6+t-9Djd2mHkO+GhisHgw07tuS6bVXrQ@mail.gmail.com> (raw)
In-Reply-To: <87imjvarez.fsf@ambrevar.xyz>
On Tue, 25 Feb 2020 at 11:32, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
> > (Note: we should remove the ‘sort’ call here as the order of packages in
> > the manifest is significant when there are file collisions.)
>
> But the export is not an "internal manifest", it should not need to know
> about package order, right?
>
> I sorted the export so that it produces a reproducible output, which is
> more version-control friendly.
IMHO, the sort would not be too expensive; even on all the packages
that Guix already includes now. ;-)
So, it does not matter too much, I guess.
However, the manifest returned is not necessary functional because the
pkg1@v1 and pkg2@v2 are not necessary provided by the same commit.
Therefore we could imagine "options" to the '--export' command, as
'--export=full' or '--export=light' etc. And even '--export=sorted'
and maybe combined as '--export=light,sorted'.
Cheers,
simon
next prev parent reply other threads:[~2020-03-03 21:44 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
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 [this message]
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
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=CAJ3okZ0s0GY66oQ+Cr6+t-9Djd2mHkO+GhisHgw07tuS6bVXrQ@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 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).