all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/7] Add Extempore.
Date: Wed, 21 Sep 2016 21:44:02 +0200	[thread overview]
Message-ID: <87fuot82d9.fsf@mdc-berlin.de> (raw)
In-Reply-To: <20160918073811.GA3983@solar>


Andreas Enge <andreas@enge.fr> writes:

> extempore only compiles on x86_64; elsewhere it fails with the message
>    CMake Error at CMakeLists.txt:82 (message):
>    Extempore currently only runs on 64-bit platforms.
> (which is not the full truth...):
>    http://hydra.gnu.org:3000/build/1473446
>
> Could you disable the other architectures?

Yes, will do.  Thanks for the note.

> Maybe this should also be done for the *-for-extempore packages, since
> there is no need to waste hydra cycles on otherwise unused packages.
> I would also hide them using "define" instead of "define-public", which
> would require to put them into the same module as extempore itself.
> What do you think?

I don’t know about hiding the packages and moving them to the same
module.  In the past we’ve kept package variants always with the
original package it was derived from,
e.g. “armadillo-for-rcpparmadillo”, which is only used for
“r-rcpparmadillo” in the “statistics” module, but which inherits from
“armadillo” in the “maths” module.

Back then I also thought that moving them together would be better, but
if I remember correctly I was asked to keep the variant with the
parent package.

I’ll disable the extempore packages for non-x86_64, but I’d like to see
some more opinions about whether to move the variants.

~~ Ricardo

  reply	other threads:[~2016-09-21 19:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  9:38 [PATCH 0/7] Add Extempore Ricardo Wurmus
2016-09-14  9:38 ` [PATCH 1/7] gnu: Add nanovg-for-extempore Ricardo Wurmus
2016-09-14 14:23   ` Thompson, David
2016-09-14  9:38 ` [PATCH 2/7] gnu: Add assimp Ricardo Wurmus
2016-09-14 14:15   ` Thompson, David
2016-09-14  9:38 ` [PATCH 3/7] gnu: Add stb-image-for-extempore Ricardo Wurmus
2016-09-14 14:16   ` Thompson, David
2016-09-14  9:38 ` [PATCH 4/7] gnu: Add llvm-for-extempore Ricardo Wurmus
2016-09-14 14:24   ` Thompson, David
2016-09-16 13:47     ` Ricardo Wurmus
2016-09-14 14:32   ` Danny Milosavljevic
2016-09-14  9:38 ` [PATCH 5/7] gnu: Add kiss-fft-for-extempore Ricardo Wurmus
2016-09-14 14:17   ` Thompson, David
2016-09-14  9:38 ` [PATCH 6/7] gnu: Add portmidi-for-extempore Ricardo Wurmus
2016-09-14 14:25   ` Thompson, David
2016-09-14 19:25     ` Ricardo Wurmus
2016-09-14  9:38 ` [PATCH 7/7] gnu: Add Extempore Ricardo Wurmus
2016-09-16 15:33 ` [PATCH 0/7] " Ricardo Wurmus
2016-09-18  7:38 ` Andreas Enge
2016-09-21 19:44   ` Ricardo Wurmus [this message]
2016-09-21 20:08     ` Efraim Flashner

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=87fuot82d9.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=andreas@enge.fr \
    --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 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.