From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add Nmap.
Date: Wed, 26 Nov 2014 00:25:22 +0100 [thread overview]
Message-ID: <873896982l.fsf@taylan.uni.cx> (raw)
In-Reply-To: <87bnnvxa0q.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 25 Nov 2014 22:09:25 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> [large snip]
>
> I hope this clarifies things.
Yes! Thanks for your patience. It now dawns on me that our primary aim
isn't byte-equal build process outputs (in terms of file contents); it's
"immutable run-time behavior" of a package. That is to say, if
/gnu/store/...-foo/bin/foo works fine today, it should work fine any
day; it's unacceptable to let it load a different .so than its
designated one, unless we define some very strict criteria for the .so
and prove that a replacement satisfies them... Similarly for some
Python module the program uses. I was chasing a "reproducible builds"
red herring.
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), then when there's an update to a run-time
component such as a DSO or dynlang module, make a new package that
merely receives some tweaks to the saved intermediate output, such as
fixing RUNPATH, re-patching shebang lines, etc. Users will still need
to download these new packages; that in turn could be improved via
binary diffs one day.
> So, where were we with this nmap patch? :-)
Heh, indeed.
I thought I'd wait for feedback from the Nmap ML but I guess that's not
necessary. I'll continue working on it tomorrow.
Taylan
next prev parent reply other threads:[~2014-11-25 23:25 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 [this message]
2014-11-26 2:01 ` Eric Bavier
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=873896982l.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--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 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.