all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Paul van der Walt <paul@denknerd.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add Mlucas.
Date: Sat, 7 Nov 2015 05:27:28 +0100	[thread overview]
Message-ID: <20151107042728.GA9731@debian.upm.edu.my> (raw)
In-Reply-To: <87twpdamn0.fsf@denknerd.org>

Hello!

I must admit I was put off looking at this patch by the addition of the
flags system, of which I do not understand the justification. Basically,
it seems to be an additional layer on top of what we already have in
our different build systems. We have #:configure-flags and #:make-flags,
and in extreme cases we can set environment variables such as CPPFLAGS
and so on in an additional phase. Commonly used flags can be added to the
build systems once and for all, for others, my impression is that we already
have the mechanisms for doing it on a per package basis. Which problem does
this part of the patch solve?

On Mon, Oct 26, 2015 at 12:34:59PM +0100, Paul van der Walt wrote:
> > * gnu/packages/mlucas.scm: New file.
> I'm not an expert, and i'm not 100% sure on this so it's an honest
> question, but does this application really deserve a new package file?
> Shouldn't mlucas perhaps be added to maths.scm?

It should go to algebra.scm, which regroups tools of symbolic, exact
computation (whereas maths.scm contains tools for numerical computation).

Andreas

  parent reply	other threads:[~2015-11-07  4:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-25  6:12 [PATCH 2/2] gnu: Add Mlucas Alex Vong
2015-10-26 11:34 ` Paul van der Walt
2015-10-26 11:49   ` Alex Vong
2015-10-26 11:56     ` Paul van der Walt
2015-11-05 21:57       ` Ludovic Courtès
2015-11-07  4:27   ` Andreas Enge [this message]
2015-11-07 12:47     ` Alex Vong
2015-11-05 22:08 ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2015-10-31 13:56 Alex Vong

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=20151107042728.GA9731@debian.upm.edu.my \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=paul@denknerd.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.