unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add mono.
Date: Fri, 22 Jul 2016 11:55:56 -0400	[thread overview]
Message-ID: <20160722155556.GB13704@jasmine> (raw)
In-Reply-To: <87r3aud7dw.fsf@gnu.org>

On Fri, Jul 15, 2016 at 09:32:43PM +0200, Jan Nieuwenhuizen wrote:
> Subject: [PATCH] gnu: Add mono.
> 
> * gnu/packages/mono.scm: New file.
> * gnu/packages/local.mk (GNU_SYSTEM_MODULES): Add it.

Thank you!

I assume this mono is working for you? I'm wondering if the problems
requiring skipped tests hide a larger problem or if it's benign.

Do you know if mono is supposed to work on all of our architectures? Or,
should we disable it on some of them?

> +              (snippet

Did you try doing these substitutions in a build phase? The origin
snippet affects what you get from `guix build --source mono`, so we tend
to reserve it for removing non-free components, so that we don't
distribute things that we don't have a right to distribute.

> +                  ;; tests fail, trying to access $HOME
> +                  (substitute* "mcs/class/Makefile"
> +                    (("^include ../build/rules.make" all)
> +                     (string-append
> +                      all
> +                      "\nrun-test-recursive:\n\t@echo skipping tests\n")))

After moving this into a build phase, there could be a prior phase
'set-env' that just sets $HOME to '/tmp'. Can you check if that works?

> +    (build-system gnu-build-system)
> +    (native-inputs
> +     `(("gettext" ,gnu-gettext)
> +       ("glib" ,glib)

I notice many uses of glib:bin rather than the full glib output. But,
to be honest, I don't understand the distinction ;)

> +     ;; these 3 tests fail
> +     `(#:make-flags
> +       `(,(string-append "PLATFORM_DISABLED_TESTS="
> +                         " appdomain-unload.exe"
> +                         " delegate2.exe"
> +                         " finally_guard.exe"
> +                         " remoting4.exe"))

4 tests?

> +       #:parallel-tests? #f))

Parallel testing is not supported? Let's add a comment.

> +    (home-page "http://mono-project.org/")

s/org/com/

  reply	other threads:[~2016-07-22 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 16:56 [PATCH] gnu: Add mono Jan Nieuwenhuizen
2016-07-15 17:01 ` Jan Nieuwenhuizen
2016-07-15 19:32   ` Jan Nieuwenhuizen
2016-07-22 15:55     ` Leo Famulari [this message]
2016-07-27 21:00       ` Jan Nieuwenhuizen
2016-07-29 14:24         ` Danny Milosavljevic
2016-07-29 16:21           ` Leo Famulari
2016-07-29 23:26             ` Danny Milosavljevic
2016-07-29 23:40               ` Leo Famulari
2016-07-30 14:57               ` Leo Famulari
2016-08-08 18:27           ` Leo Famulari

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=20160722155556.GB13704@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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).