From: Reza Housseini <reza.housseini@gmail.com>
To: Greg Hogan <code@greghogan.com>
Cc: help-guix@gnu.org
Subject: Re: How to pack development inputs from a package
Date: Mon, 23 Sep 2024 20:56:27 +0200 [thread overview]
Message-ID: <87y13iyzac.fsf@housseini.me> (raw)
In-Reply-To: <CA+3U0ZnMGHK=FR0k8gNfRL43kd76PVGMT_L71ZsfeBnO+D64Bw@mail.gmail.com>
Greg Hogan <code@greghogan.com> writes:
Hi Ian, hi Greg
Thanks for your inputs, I tried to come up with an expression, but
failed to find one working, I got stuck with
guix pack -f docker -e '(@ (guix packages) (package-development-inputs (load "guix.scm")))'
but it does not seem to work.
I managed to make it work with an additional manifest.scm file with the
following content
(package->development-manifest (load "guix.scm"))
although I would have prefered the command line approach as I need to
call guix pack inside a script.
Thanks and all the best,
Reza
> On Fri, Sep 20, 2024 at 9:47 AM Reza Housseini <reza.housseini@gmail.com> wrote:
>>
>> Hi Guixers
>>
>> From guix shell I can call
>>
>> guix shell -D -f guix.scm
>>
>> Now I want to pack those into a container with guix pack, but there is
>> no equivalent command there, how would I achieve this, is there an
>> expression I could use?
>>
>> Something along the way
>>
>> guix pack -f docker -e '(package->development-manifest (from-file "guix.scm"))'
>
> You have a manifest for the package, why not create a second manifest
> for the container which includes guix.scm and returns the result of
> package->development-manifest (or returns that concatenated with
> additional useful development packages)?
prev parent reply other threads:[~2024-09-23 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 13:46 How to pack development inputs from a package Reza Housseini
2024-09-21 3:21 ` Ian Eure
2024-09-23 14:08 ` Greg Hogan
2024-09-23 18:56 ` Reza Housseini [this message]
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=87y13iyzac.fsf@housseini.me \
--to=reza.housseini@gmail.com \
--cc=code@greghogan.com \
--cc=help-guix@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.