From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, zimoun <zimon.toutoune@gmail.com>,
Konrad Hinsen <konrad.hinsen@fastmail.net>,
Anthony Quizon <anthoq88@gmail.com>
Subject: Re: Building packages in REPL
Date: Fri, 26 Jun 2020 06:17:55 -0400 [thread overview]
Message-ID: <D6D026B5-2724-423D-8A54-E9380D29FDE4@lepiller.eu> (raw)
In-Reply-To: <86wo3u9mfi.fsf@gmail.com>
Le 26 juin 2020 06:00:17 GMT-04:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Dear,
>
>On Fri, 26 Jun 2020 at 09:25, Konrad Hinsen
><konrad.hinsen@fastmail.net> wrote:
>> Anthony Quizon <anthoq88@gmail.com> writes:
>>
>>> Is there a way that I can build a package via the repl?
>
>Well, it is not what you are asking I guess, but it is possible:
>
>--8<---------------cut here---------------start------------->8---
>$ guix repl
>scheme@(guix-user)> (use-modules (guix scripts build))
>scheme@(guix-user)> (guix-build "-L" "." "bonjour")
>/gnu/store/m658csbnly6zywfl5nax9glya3rzhbdy-bonjour-2.10
>--8<---------------cut here---------------end--------------->8---
>
>And there is no '~' expansion so "-L" "~/somewhere" does not work.
>
>> As far as I know, no. I have been looking for this as well,
>> in order to make package development more interactive.
>
>Well, I do not know enough the API but it should be added and exposed
>if
>it does not exist yet. And the question is which level of granularity?
>
>
>>> For example,
>>> If I had a channel with a custom package in it, can I do:
>>>
>>> `$ guix repl -L .`
>>> `> ,use (my-channel packages base) `
>>> `> (build-package my-package) ;; this is the example imaginary
>command `
>
>The entry point is "(guix scripts build)".
>
>> I'd even want more: access to the individual build steps.
>
>Do you mean the "phases"?
>
>
>All the best,
>simon
One way to do this with the guix API is to get the derivation, then build it:
(use-modules (guix derivations) (guix store) (gnu packages bash))
(define package bash-minimal)
(define store (open-connection))
(define der (package-derivation store package))
(build-derivations store (list der))
Is that what you want?
next prev parent reply other threads:[~2020-06-26 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 5:13 Building packages in REPL Anthony Quizon
2020-06-26 7:25 ` Konrad Hinsen
2020-06-26 10:00 ` zimoun
2020-06-26 10:17 ` Julien Lepiller [this message]
2020-06-26 10:44 ` zimoun
2020-07-24 14:38 ` Ludovic Courtès
2020-07-27 14:13 ` Pierre Neidhardt
2020-07-27 23:30 ` zimoun
2021-03-20 10:57 ` Xinglu Chen
2020-06-26 14:26 ` Efraim Flashner
2020-06-30 7:58 ` Anthony Quizon
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=D6D026B5-2724-423D-8A54-E9380D29FDE4@lepiller.eu \
--to=julien@lepiller.eu \
--cc=anthoq88@gmail.com \
--cc=help-guix@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=zimon.toutoune@gmail.com \
/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.
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).