unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Profile hook in build environment?
Date: Thu, 10 Sep 2020 09:24:37 +0200	[thread overview]
Message-ID: <87bliert56.fsf@yamatai> (raw)
In-Reply-To: <87y2ljbaft.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]


Ricardo Wurmus <rekado@elephly.net> skribis:

> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> Is there a way to generate files and add them to the environment created
>> by 'guix build' as it can be done with profile hooks?
>
> Yes, the build system can do whatever it wants.  The
> texlive-build-system, for example, builds a union directory from all TeX
> Live inputs and then modifies the configuration file.

Thanks for the pointer, it has been very useful.


Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Hi Guillaume,
>
> Thanks for taking a shot at this ;)
>
> Why would we need to generate the ASDF configuration file in a hook?
> Can't we do it at build time?
>
> Cheers!

I got rid of the hook and now I'm creating all the required files/links
at build time in 'etc/common-lisp/source-registry.conf.d/' and in
'etc/common-lisp/asdf-output-translations.conf.d/'.
It seems to work well with packages having simple definitions. Now
I have to check and adapt the more complex ones.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-09-10  7:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09  8:19 Profile hook in build environment? Guillaume Le Vaillant
2020-09-09  8:35 ` Pierre Neidhardt
2020-09-09  8:50 ` Ricardo Wurmus
2020-09-10  7:24   ` Guillaume Le Vaillant [this message]
2020-09-10  9:57     ` Pierre Neidhardt

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=87bliert56.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).