From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] update haunt to 0.2.1
Date: Wed, 25 Jan 2017 19:03:54 +0100 [thread overview]
Message-ID: <8737g7vwxh.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=Rwfa3E-LESg7pR0vKPK7i5DaN7v5PXOYbui-rxp=_ASOctQ@mail.gmail.com> (David Thompson's message of "Wed, 25 Jan 2017 11:03:05 -0500")
Howdy David!
"Thompson, David" <dthompson2@worcester.edu> skribis:
> On Tue, Jan 24, 2017 at 5:12 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Catonano <catonano@gmail.com> skribis:
>>
>>> From 015719506600bcb674b1d47398af27c2b4f32d18 Mon Sep 17 00:00:00 2001
>>> From: humanitiesNerd <catonano@gmail.com>
>>> 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.)
Ludo’.
next prev parent reply other threads:[~2017-01-25 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 14:11 [PATCH] update haunt to 0.2.1 Catonano
2017-01-24 20:49 ` Catonano
2017-01-24 21:00 ` Leo Famulari
2017-01-24 22:12 ` Ludovic Courtès
2017-01-25 16:03 ` Thompson, David
2017-01-25 18:03 ` Ludovic Courtès [this message]
2017-03-01 17:02 ` Catonano
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=8737g7vwxh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
/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).