all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@gmail.com>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add Nmap.
Date: Tue, 25 Nov 2014 20:01:52 -0600	[thread overview]
Message-ID: <CADwNbn89TuodVmip_Etqzb2R=Au=1mM7W=XPpjikwrQkMP_mgw@mail.gmail.com> (raw)
In-Reply-To: <873896982l.fsf@taylan.uni.cx>

[-- Attachment #1: Type: text/plain, Size: 757 bytes --]

On Tue, Nov 25, 2014 at 5:25 PM, Taylan Ulrich Bayırlı/Kammer <
taylanbayirli@gmail.com> wrote:

>
> That being said, I still think it's wasteful that C code gets recompiled
> when there's an update to a dynamic component.
>
> A rough idea for the future: save some intermediate build output (say
> from the 'build' phase)
>

I added the ccache package a little while ago.  I had wondered whether it
would be possible to run all our builds through ccache so that updates to
core packages might not be as much of a time burden (at the cost of some
extra disk space).  Might be something interesting to try.

`~Eric

-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

[-- Attachment #2: Type: text/html, Size: 1244 bytes --]

      reply	other threads:[~2014-11-26  2:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 22:05 [PATCH] gnu: Add Nmap "Taylan Ulrich Bayırlı/Kammer"
2014-11-23  9:02 ` Andreas Enge
2014-11-23 11:54   ` Taylan Ulrich Bayırlı/Kammer
2014-11-23 20:38     ` Ludovic Courtès
2014-11-23 23:51       ` Taylan Ulrich Bayırlı/Kammer
2014-11-24 14:22         ` Ludovic Courtès
2014-11-24 20:52           ` Taylan Ulrich Bayırlı/Kammer
2014-11-25 21:09             ` Ludovic Courtès
2014-11-25 23:25               ` Taylan Ulrich Bayırlı/Kammer
2014-11-26  2:01                 ` Eric Bavier [this message]

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='CADwNbn89TuodVmip_Etqzb2R=Au=1mM7W=XPpjikwrQkMP_mgw@mail.gmail.com' \
    --to=ericbavier@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=taylanbayirli@gmail.com \
    /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.