all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 03/07: gnu: libfive: Add snippet, enable tests and remove obsolete phase.
Date: Thu, 19 Apr 2018 17:19:48 +0200	[thread overview]
Message-ID: <87zi1zi5pn.fsf@gnu.org> (raw)
In-Reply-To: <87in8nidqp.fsf@netris.org> (Mark H. Weaver's message of "Thu, 19 Apr 2018 08:26:22 -0400")

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> civodul pushed a commit to branch master
>> in repository guix.
>>
>> commit 0818c01aefbaa7ecce5e310ec5f70886850a7f9c
>> Author: Diego Nicola Barbato <dnbarbato@posteo.de>
>> Date:   Fri Apr 6 13:43:54 2018 +0200
>>
>>     gnu: libfive: Add snippet, enable tests and remove obsolete phase.
>>     
>>     * gnu/packages/engineering.scm (libfive)[source]: Add snippet to
>>     remove bundled catch.
>
> [...]
>
>> +                (snippet
>> +                 ;; Remove bundled catch since we provide our own.
>> +                 '(delete-file "libfive/test/catch.hpp"))))
>
> It would be good to try to avoid adding more phases or snippets that
> return unspecified values.  I fixed every snippet in 'core-updates', but
> I guess more passes will be needed as these errors continue to be
> introduced.

Right, apologies for that; I’ve fixed this particular instance.

I look forward to the day where we can ignore those return values and
assume an exception is thrown when something goes wrong.  Thankfully the
work you’ve been doing on ‘core-updates’ should help us get there!

Ludo’.

      reply	other threads:[~2018-04-19 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180419095903.21090.36781@vcs0.savannah.gnu.org>
     [not found] ` <20180419095904.D9E2D204EE@vcs0.savannah.gnu.org>
2018-04-19 12:26   ` 03/07: gnu: libfive: Add snippet, enable tests and remove obsolete phase Mark H Weaver
2018-04-19 15:19     ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zi1zi5pn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.