all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: Guix-devel <guix-devel@gnu.org>,
	federico.beffa@gmail.com, Federico Beffa <beffa@ieee.org>
Subject: Re: [PATCH 0/2] native-search-paths for GHC
Date: Thu, 08 Oct 2015 14:00:47 +0200	[thread overview]
Message-ID: <87a8rttvrk.fsf@gnu.org> (raw)
In-Reply-To: <de8e0cc2e54f6b640d4a4930e17bff81@openmailbox.org> (Eric Bavier's message of "Wed, 07 Oct 2015 16:27:11 -0500")

Eric Bavier <ericbavier@openmailbox.org> skribis:

> On 2015-10-07 11:07, Federico Beffa wrote:

[...]

>> * If I understand correctly, the configuration files of dependencies
>> are
>>   copied in a unique directory for each package.  Instead of copying
>>   would a symlink work? (There are literally thousands of packages on
>>   Hackage and hopefully Guix will get more of them.)
>
> I don't know if symlinking is allowed across store directories, though
> if it is, that'd be something to try.

Yes it’s allowed.  That’s what ‘union-build’ (the procedure that builds
profiles) does.

>> * Some Haskell libraries have a rather large list of dependencies. For
>>   this reason I can imagine that in some situations GHC_PACKAGE_PATH
>>   could grow rather long.
>
> Not every package would end up with an entry in GHC_PACKAGE_PATH, only
> those that are installed, or declared inputs.  Dependent libraries
> would be found when GHC examines the package databases of those
> packages.
>
>>   This thought made me wonder if there is a
>>   maximum length to the value of environment variables that we could
>>   possibly hit.
>
> We've already pushed this quite far.  E.g. the hydra package creates a
> rather sizable PER5LIB path.

Nice.  :-)

AFAIK there’s no limit on the size of an environment variable’s value.

However, it’s a good idea to keep search paths small, to reduce the
number of ‘stat’ calls that have to be done before a given file is
found.

Using a symlink forest is a good way to achieve that.

Thanks,
Ludo’.

  reply	other threads:[~2015-10-08 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 16:07 [PATCH 0/2] native-search-paths for GHC Federico Beffa
2015-10-07 21:27 ` Eric Bavier
2015-10-08 12:00   ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-06 21:26 ericbavier
2015-10-16 13:35 ` 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=87a8rttvrk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@ieee.org \
    --cc=ericbavier@openmailbox.org \
    --cc=federico.beffa@gmail.com \
    --cc=guix-devel@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.