unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gregor Giesen <giesen@zaehlwerk.net>
To: help-guix@gnu.org
Subject: Re: Extra files in build container
Date: Sat, 17 Jun 2017 08:58:48 +0200	[thread overview]
Message-ID: <20170617065848.cfevrq6bpgsa2vlt@zaehlwerk.net> (raw)
In-Reply-To: <87y3ssicsg.fsf@gnu.org>

Dear Ludo’,

thanks for the help!

On Fri, Jun 16, 2017 at 09:58:55AM +0200, Ludovic Courtès wrote:
> In cases like the one you describe, we usually end up modifying tests to
> use the numerical values for services and protocols rather than their
> names.
Unfortunately, this turns out to be quite cumbersome since in my case
(unittests for unbound) there is a lot of test data to be modified and
in many cases not only plain text but also encrypted records (DNSSEC 
tests). On the other hand the values to be looked up are mostly “udp”
and “tcp” in /etc/protocols and “domain” in /etc/services, so I decided 
that using a preload library for these few glibc calls just in case of 
the unittest should do the trick rather than no checks at all. However, 
it is an ugly hack and bloats the package definition.

> It would probably make sense to allow derivations to populate /etc
> though.
That might help!

Many thanks to all contributers for this very nice peace of software!

Best,
Gregor

  reply	other threads:[~2017-06-17  6:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15  7:29 Extra files in build container Gregor Giesen
2017-06-16  7:58 ` Ludovic Courtès
2017-06-17  6:58   ` Gregor Giesen [this message]
2017-06-19 11:26     ` Ludovic Courtès
2017-06-19 11:44       ` Gregor Giesen
2017-06-19 14:49         ` Ludovic Courtès
2017-06-19 16:48           ` Gregor Giesen
2017-06-19 21:21             ` Ludovic Courtès

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=20170617065848.cfevrq6bpgsa2vlt@zaehlwerk.net \
    --to=giesen@zaehlwerk.net \
    --cc=help-guix@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.
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).