unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add LAPACKE
Date: Wed, 13 Jul 2016 14:22:12 +0200	[thread overview]
Message-ID: <878tx5iv7v.fsf@mdc-berlin.de> (raw)
In-Reply-To: <87k2gqhogo.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
>> here's an alternative to the patch provided here:
>>
>>     https://lists.gnu.org/archive/html/guix-devel/2016-06/msg00099.html
>>
>> Instead of building LAPACKE as part of the lapack package this patch adds a
>> new package "lapack-with-lapacke".  I did this because an increase in closure
>> size of 20MiB is a little much for a commonly used package, in my opinion.
>
> The 20MiB increase shown in the message above correspond mostly to
> gcc:lib, which is present anyway, so I would say it’s acceptable.

Well, in this case I’ll just apply Dave’s patch then (see email in the
ML archive).

“guix refresh -l lapack” shows me that 51 packages are affected, which
results in a rebuild of 86 dependent packages.  Okay to push to master?

~~ Ricardo

  reply	other threads:[~2016-07-13 12:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 15:40 [PATCH] Add LAPACKE Ricardo Wurmus
2016-07-08 15:40 ` [PATCH] gnu: Add lapack-with-lapacke Ricardo Wurmus
2016-07-11  9:17 ` [PATCH] Add LAPACKE Ricardo Wurmus
2016-07-12 13:45   ` Ricardo Wurmus
     [not found] ` <20160710142058.GA5924@solar>
2016-07-11  9:23   ` Ricardo Wurmus
2016-07-12 15:21 ` Ludovic Courtès
2016-07-13 12:22   ` Ricardo Wurmus [this message]
2016-07-14 16:15     ` Andreas Enge
2016-07-17 15:52       ` Ricardo Wurmus

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=878tx5iv7v.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).