unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Frederick Muriithi <fredmanglis@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add ldc-1.1.0-beta6
Date: Mon, 09 Jan 2017 15:41:40 +0100	[thread overview]
Message-ID: <87y3ykmh23.fsf@gnu.org> (raw)
In-Reply-To: <CALjrZwYS0FzDcHRVM6cfN5Vfv=9y-n=EnU64qQvLJV-R_LCwdA@mail.gmail.com> (Frederick Muriithi's message of "Fri, 6 Jan 2017 18:04:38 +0300")

Hello!

Sorry for the late reply!

Frederick Muriithi <fredmanglis@gmail.com> skribis:

> Based on thread
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg00465.html
>
> - Fixed some issues raised by Danny Milosavljevic on thread above
> - Updated the beta version to 6, up from 4
> - Started up a thread on ldc forum to have a version flag added to
> deactivate network tests when building ldc
> https://forum.dlang.org/post/zmdbdgnzrxyvtpqafvyg@forum.dlang.org

Nice!

> From a0185dc1f5881bae8094643251335b04560900a0 Mon Sep 17 00:00:00 2001
> From: Muriithi Frederick Muriuki <fredmanglis@gmail.com>
> Date: Fri, 6 Jan 2017 17:51:18 +0300
> Subject: [PATCH] gnu: Add ldc-1.1.0-beta6
>
> * gnu/packages/ldc.scm (ldc-1.1.0-beta6): New variable
> * gnu/packages/ldc.scm (ldc-beta): New variable
> * gnu/packages/patches/ldc1.1.0-disable-dmd-tests.patch: New patch
> * gnu/packages/patches/ldc1.1.0-disable-phobos-tests.patch: New patch

Overall the patch looks good to me.

One question: We usually avoid packaging software that has no release or
has an “alpha” or “beta” label.  Do you think we could wait for 1.1.0 to
be officially released?  Or are there good reasons why we should not
wait?

Some minor issues:

> +(define-public ldc-1.1.0-beta6
> +  (let ((older-version "1.1.0-beta4"))

[...]

> +       ("phobos-src"
> +        ,(origin
> +           (method url-fetch)
> +           (uri (string-append
> +                 "https://github.com/ldc-developers/phobos/archive/ldc-v"
> +                 older-version ".tar.gz"))
> +           (sha256
> +            (base32
> +             "1iwy5rs0rqkicj1zfsa5yqvk8ard99bfr8g69qmhlbzb98q0kpks"))
> +           (patches (search-patches "ldc1.1.0-disable-phobos-tests.patch"))))
> +       ("druntime-src"
> +        ,(origin
> +           (method url-fetch)
> +           (uri (string-append
> +                 "https://github.com/ldc-developers/druntime/archive/ldc-v"
> +                 older-version ".tar.gz"))
> +           (sha256
> +            (base32
> +             "1qsiw5lz1pr8ms9myjf8b94nqi7f1781k226jvxwnhkjg11d0s63"))))
> +       ("dmd-testsuite-src"
> +        ,(origin
> +           (method url-fetch)
> +           (uri (string-append
> +                 "https://github.com/ldc-developers/dmd-testsuite/archive/ldc-v"
> +                 older-version ".tar.gz"))
> +           (sha256
> +            (base32
> +             "0jp54hyi75i9g41rvgmm3zg21yzv57q8dghrhb432rb0n9j15mbp"))
> +           ;; Deactivate some failing gdb tests. Most other gdb tests pass
> +           (patches (search-patches "ldc1.1.0-disable-dmd-tests.patch")))))))))

Could you add a comment explaining why the previous version of these is
needed, instead of the current version?

> --- /dev/null
> +++ b/gnu/packages/patches/ldc1.1.0-disable-dmd-tests.patch

Could you add a line or two explaining at the top of patch explaining
what it does and why, and what its upstream status is?

For example, I think this one disables a test that would require GDB,
which is not an input (?), and presumably it won’t be submitted
upstream.

> @@ -0,0 +1,28 @@
> +diff --git a/d_do_test.d b/d_do_test.d
> +index aa67169..7a4dcc1 100755
> +--- a/d_do_test.d
> ++++ b/d_do_test.d
> +@@ -645,8 +645,8 @@ int main(string[] args)
> +                     auto gdb_output = execute(fThisRun, command, true, result_path);
> +                     if (testArgs.gdbMatch !is null)
> +                     {
> +-                        enforce(match(gdb_output, regex(testArgs.gdbMatch)),
> +-                                "\nGDB regex: '"~testArgs.gdbMatch~"' didn't match output:\n----\n"~gdb_output~"\n----\n");
> ++                        //enforce(match(gdb_output, regex(testArgs.gdbMatch)),
> ++                                //"\nGDB regex: '"~testArgs.gdbMatch~"' didn't match output:\n----\n"~gdb_output~"\n----\n");

I think it’s better to just delete the two lines instead of commenting
them out: that makes the patch easier to read.

Hope this makes sense.

Thanks for your contribution!

Ludo’.

  parent reply	other threads:[~2017-01-09 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 15:04 [PATCH] gnu: Add ldc-1.1.0-beta6 Frederick Muriithi
2017-01-07 16:32 ` Pjotr Prins
2017-01-09 14:41 ` Ludovic Courtès [this message]
2017-01-10  5:55   ` Frederick Muriithi
2017-01-10 14:36   ` Frederick Muriithi
2017-01-12 14:09     ` Ludovic Courtès
2017-01-17 12:58       ` Frederick Muriithi
2017-01-19 12:47         ` Ludovic Courtès
     [not found]           ` <CALjrZwaJnPN5B5PoLX5Xf56m93nOev5xaydeYYP32sg+88ZzAA@mail.gmail.com>
     [not found]             ` <CALjrZwbB__c8_VVETcurMxKeP4n3iyN70SpuAexp3jJXAGn8eg@mail.gmail.com>
     [not found]               ` <CALjrZwY9gNvP_KbmhrR1V+oKxV=RFOCWeqfjQvMZ0t0HX5tEhg@mail.gmail.com>
     [not found]                 ` <CALjrZwapZQtNvdp-KGBUGD6UM34RZxO3Xvqwe=++xGqNvqUE6A@mail.gmail.com>
     [not found]                   ` <CALjrZwavQ0sTw3Ds8ALpYbppvfbNevj7c7vQjqn7uJqY0hqxaA@mail.gmail.com>
     [not found]                     ` <CALjrZwb2iZPcce+vkVoTGfq7dZZ+zbxz3TyxN5L+Uq_cwiO_MQ@mail.gmail.com>
2017-01-19 13:00                       ` Frederick Muriithi
2017-01-20 13:33                         ` Ludovic Courtès
2017-01-22  9:27                           ` Frederick Muriithi
2017-01-28  0:28                             ` Ludovic Courtès
2017-01-19 11:02   ` Pjotr Prins
2017-01-28  6:09     ` Pjotr Prins

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=87y3ykmh23.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=fredmanglis@gmail.com \
    --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).