From: "Bonface M. K." <bonfacemunyoki@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org, Pjotr Prins <pjotr2020@thebird.nl>
Subject: Re: How do you write a package's deps to a file?
Date: Tue, 01 Dec 2020 11:29:06 +0300 [thread overview]
Message-ID: <86o8jeexpp.fsf@gmail.com> (raw)
In-Reply-To: <D5CB7294-94CA-4698-9612-F5609FAE8129@lepiller.eu> (Julien Lepiller's message of "Mon, 30 Nov 2020 12:17:30 -0500")
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Hi!
Julien Lepiller <julien@lepiller.eu> writes:
> The reason you always get the same data is because
> you're assigning "name" inside the sexp
> (build-side), but you're using it inside tge
> unquote (host-side), so it refers to the name of
> the package you're building.
>
Ah yes! I see that now. Silly me ~.~
> I think you're doing it wrong, because some input
> names have no corresponding package (see source
> for instance). Why not use the package data
> directly, like guix graph does for instance?
>
I don't know how to do this. I've had a look at
guix/graph.scm and scripts/graph.scm... And I got
lost--- I'm not /yet/ a scheme guru... I reckon
I'll go with Efraim's suggestion which seems
easier to do :)
Thanks for the pointers!
[...]
--
Bonface M. K. <https://www.bonfacemunyoki.com>
Chief Emacs Bazu / Rieng ya software sare
Mchochezi of: <https://upbookclub.com> / Twitter: @BonfaceKilz
GPG Key: D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next prev parent reply other threads:[~2020-12-01 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 16:25 How do you write a package's deps to a file? Bonface M. K.
2020-11-30 17:17 ` Julien Lepiller
2020-11-30 23:23 ` zimoun
2020-12-01 9:13 ` Bonface M. K.
2020-12-01 9:59 ` zimoun
2020-12-01 18:04 ` Bonface M. K.
2020-12-01 8:29 ` Bonface M. K. [this message]
2020-12-01 7:35 ` Efraim Flashner
2020-12-01 9:15 ` Bonface M. K.
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=86o8jeexpp.fsf@gmail.com \
--to=bonfacemunyoki@gmail.com \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=pjotr2020@thebird.nl \
/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).