From: zimoun <zimon.toutoune@gmail.com>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix environment ad-hoc manifests
Date: Thu, 22 Oct 2020 18:22:46 +0200 [thread overview]
Message-ID: <CAJ3okZ2UeDP+bsMMRCPzMz3LNYjGY_NHqFH=-O44LaFrkLkn1g@mail.gmail.com> (raw)
In-Reply-To: <20201022123929.6ca21e85@pantherx.org>
Dear,
On Thu, 22 Oct 2020 at 11:10, Reza Alizadeh Majd <r.majd@pantherx.org> wrote:
> working with guix environments, we can pass list of packages, using a
> manifest file. we also can use --ad-hoc switch for additional packages
> we need to add to the prepared environment.
>
> it would also be great to be able to pass list of ad-hoc packages,
> using a manifest file, something like --ad-hoc-manifest switch. or
> maybe there is such option already available that I missed.
From my understanding, as Ricardo said, the command:
guix environment -m my-manifest.scm
is equivalent to:
guix environment --ad-hoc pkg1 pkg2 pkg3
And moreover, you can also do:
guix environment -m my-manifest.scm --ad-hoc my-package
What could be missing is to pass a manifest file and provide all the
required packages used to build all the packages listed in the
manifest. Other said, there is no equivalent at the manifest level
of:
guix environment pkg1 pkg2 pkg3
or even this:
guix environment pkg1 pkg2 pkg3 --ad-hoc pkg4 pkg5 pkg6
To be clear, it is possible but the API is not straightforward.
Is it what you mean?
Hope that helps,
simon
next prev parent reply other threads:[~2020-10-22 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 9:09 guix environment ad-hoc manifests Reza Alizadeh Majd
2020-10-22 11:53 ` Ricardo Wurmus
2020-10-22 13:08 ` Reza Alizadeh Majd
2020-10-22 15:16 ` Ricardo Wurmus
2020-10-24 7:35 ` Reza Alizadeh Majd
2020-10-22 16:22 ` zimoun [this message]
2020-10-24 7:52 ` Reza Alizadeh Majd
[not found] <mailman.85.1603382448.9180.help-guix@gnu.org>
2020-10-22 20:05 ` Zelphir Kaltstahl
2020-10-22 20:17 ` 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='CAJ3okZ2UeDP+bsMMRCPzMz3LNYjGY_NHqFH=-O44LaFrkLkn1g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=r.majd@pantherx.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.