From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 54393@debbugs.gnu.org
Subject: [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests
Date: Tue, 15 Mar 2022 10:53:44 +0100 [thread overview]
Message-ID: <a0e20f6b587fbb2fa8699b37ae119c1009627f90.camel@ist.tugraz.at> (raw)
In-Reply-To: <874k3zmup2.fsf_-_@gnu.org>
Am Dienstag, dem 15.03.2022 um 10:27 +0100 schrieb Ludovic Courtès:
> Hi,
>
> Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> skribis:
>
> > The current implementation is missing the most important feature,
> > which would be ‘guix manifest --profile $GUIX_PROFILE’ :)
>
> True, we could add ‘-p’ and make it equivalent to ‘guix package
> --export-manifest’.
>
> I think lack of ‘-p’ is not a showstopper though since ‘guix package
> --export-manifest’ remains available.
True, but implementing it as part of ‘guix manifest’ would open up a
way to easily declare a manifest for “merged” profiles. These could be
applied in integration testing, e.g. you could merge multiple profiles
together and watch for intended and unintended side effects, for
instance regarding search paths.
> > Furthermore, one issue I have with both the existing and proposed
> > approaches is that both mandate the specification style,
>
> The reasons for the specification style are:
>
> 1. That it’s easier to implement reliably, since you just need to
> rely on package specs.
>
> 2. The resulting code is future-proof: if packages are moved from
> one module to another, or if their variables are renamed, it
> still works.
>
> 3. It’s a one-to-one mapping compared to the command line, which
> hopefully makes it clearer.
>
> However, ‘manifest->code’ existed before this patch series, so I
> think it’s beyond the scope of this review.
It's true that it's out of scope, but I don't want this to be
forgotten. I can see the rationale of specification style for user
profiles, but for version-controlled package development manifests,
there are different incentives in play. For example, you might want to
make sure that a package uses gcc-toolchain from (gnu packages
commencement) and not (google monorepo cc).
Cheers
next prev parent reply other threads:[~2022-03-15 9:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 21:50 [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Ludovic Courtès
2022-03-14 21:51 ` [bug#54393] [PATCH 1/2] packages: Add 'package-unique-version-prefix' Ludovic Courtès
2022-03-14 21:51 ` [bug#54393] [PATCH 2/2] Add 'guix manifest' Ludovic Courtès
2022-03-15 7:18 ` [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Liliana Marie Prikler
2022-03-15 9:27 ` Ludovic Courtès
2022-03-15 9:53 ` Liliana Marie Prikler [this message]
2022-03-15 15:17 ` Ludovic Courtès
2022-03-15 9:00 ` zimoun
2022-03-15 9:23 ` Ludovic Courtès
2022-03-15 10:21 ` zimoun
2022-03-15 19:38 ` Ludovic Courtès
2022-03-31 11:09 ` [bug#54393] [PATCH v2 1/3] packages: Add 'package-unique-version-prefix' Ludovic Courtès
2022-03-31 11:09 ` [bug#54393] [PATCH v2 2/3] environment: Export 'load-manifest' Ludovic Courtès
2022-03-31 11:09 ` [bug#54393] [PATCH v2 3/3] shell: Add '--export-manifest' Ludovic Courtès
2022-04-04 14:37 ` [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Maxim Cournoyer
2022-04-04 21:16 ` bug#54393: " Ludovic Courtès
2022-04-05 5:48 ` [bug#54393] " zimoun
2022-04-06 8:08 ` Ludovic Courtès
2022-03-31 11:10 ` [bug#54393] [PATCH v2 0/3] Add '--export-manifest' to 'guix shell' Ludovic Courtès
2022-03-15 16:50 ` [bug#54393] [PATCH 0/2] Add 'guix manifest' to "translate" commands to manifests Greg Hogan
2022-03-16 9:58 ` Ludovic Courtès
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=a0e20f6b587fbb2fa8699b37ae119c1009627f90.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=54393@debbugs.gnu.org \
--cc=ludo@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.