Edouard Klein writes:
> As you can see a bit below where I linked before, you can redefine the test
> stage in order to set the correct environment variables before calling
> your test command. It will be a bit redundant with the wrapping phase,
> but it would allow you not to edit your
On Tue, Aug 17, 2021 at 08:49:27PM +0200, Edouard Klein wrote:
> It does, thanks, but I'm in a bit of a pickle there because this
> packagge needs, for reasons outside of my control, to be deployable on
> a multitude of host (non-GuixSD) linux distributions, and as a docker
> container. In those
Leo Famulari writes:
> On Tue, Aug 17, 2021 at 04:01:15PM +0200, Edouard Klein wrote:
>> See e.g.
>> https://gitlab.com/edouardklein/guix/-/blob/beaverlabs/beaver/packages/scheme-xyz.scm#L68
>>
>> Here, xlsxio and tzdir will be expanded to their full install path in
>> the store.
>
> I'm going
Phil writes:
> Thanks for comments Edouard! Responses inline.
:)
>
>
> Edouard Klein writes:
>
>
>> See e.g.
>> https://gitlab.com/edouardklein/guix/-/blob/beaverlabs/beaver/packages/scheme-xyz.scm#L68
>
> Ahh so wrap-program creates a script that sets the two env vars
> LD_LIBRARY_PATH and
On Tue, Aug 17, 2021 at 04:01:15PM +0200, Edouard Klein wrote:
> See e.g.
> https://gitlab.com/edouardklein/guix/-/blob/beaverlabs/beaver/packages/scheme-xyz.scm#L68
>
> Here, xlsxio and tzdir will be expanded to their full install path in
> the store.
I'm going off-topic, but you should not
Thanks for comments Edouard! Responses inline.
Edouard Klein writes:
> See e.g.
> https://gitlab.com/edouardklein/guix/-/blob/beaverlabs/beaver/packages/scheme-xyz.scm#L68
Ahh so wrap-program creates a script that sets the two env vars
LD_LIBRARY_PATH and TZDIR before calling the original
Hi !
I side-step this kind of things by adding a stage in package-y that will
find and replace all references to "bar" with the complete path to the
installation path of package-x, or that will set the needed environment
variable to the full path of the dependency.
See e.g.
Hi all,
I have some platform independent files I have created a package for using
copy-build-system. This works great but I've come across situation I don't
know how to handle.
Let's call the package I've made package-x, and let's say that package-y
(which is for arguments sake is a python
