From: "Bonface M. K." <bonfacemunyoki@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
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 12:15:07 +0300 [thread overview]
Message-ID: <86ft4pga5g.fsf@gmail.com> (raw)
In-Reply-To: <X8XyKjLaG4nEe+Kl@E5400> (Efraim Flashner's message of "Tue, 1 Dec 2020 09:35:06 +0200")
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Hi Efraim!
Efraim Flashner <efraim@flashner.co.il> writes:
[...]
>> Notice that the version, home page and description
>> are repeated across rows. Herein lies my question:
>> How would you fetch the details of the inputs(like
>> version, home-page, description) etc etc from a
>> modifed phase. Do I need to create a closure from
>> which I can import the modules like say _(use (gnu
>> packages))_. How do I do that if that's the case?
>>
>> Is it also possible to get the same information in
>> a fine grained manner, like say get the
>> propagated-inputs instead of getting /all/ inputs?
>>
>
> I think it would be easiest to compute this outside the package
> definition and then add it as an input and just plop the precomputed
> file into place in a custom phase.
Yes! I think this will do it for this case. Would
never have thought of that! Thanks!
--
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 --]
prev parent reply other threads:[~2020-12-01 9:15 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.
2020-12-01 7:35 ` Efraim Flashner
2020-12-01 9:15 ` Bonface M. K. [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
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=86ft4pga5g.fsf@gmail.com \
--to=bonfacemunyoki@gmail.com \
--cc=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--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).