[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] update haunt to 0.2.1

From: Ludovic Courtès
Subject: Re: [PATCH] update haunt to 0.2.1
Date: Wed, 25 Jan 2017 19:03:54 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

Howdy David!

"Thompson, David" <address@hidden> skribis:

> On Tue, Jan 24, 2017 at 5:12 PM, Ludovic Courtès <address@hidden> wrote:
>> Catonano <address@hidden> skribis:
>>> From 015719506600bcb674b1d47398af27c2b4f32d18 Mon Sep 17 00:00:00 2001
>>> From: humanitiesNerd <address@hidden>
>>> Date: Tue, 24 Jan 2017 14:55:12 +0100
>>> Subject: [PATCH] gnu: haunt: Update to 0.2.1
>>> * gnu/packages/guile.scm (haunt): Update to 0.2.1.
>> Applied, thanks.  :-)
>>>      (propagated-inputs
>>> -     `(("guile-reader" ,guile-reader)))
>>> +     `(("guile-reader" ,guile-reader)
>>> +       ("guile-commonmark" ,guile-commonmark)))
>> We could (should?) avoid this by augmenting the ‘wrap-haunt’ phase.
>> Thoughts?
> Agreed, but even better would be if I knew how to make upstream just
> do the right thing to begin with. ;)  Do you know how this could be
> done?

For Haunt’s own modules, you could set the right search path in the
‘haunt’ command itself, like the Shepherd and Guix do.

For these external dependencies, you could always use ‘search-path’ at
configure time to hard-wire their locations in ‘haunt’ as well.  (Guix
does not do that and I don’t know of any project that does, but IWBN.)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]