From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ‘core-updates’ is back!
Date: Tue, 29 Aug 2017 11:14:07 +0200 [thread overview]
Message-ID: <87val6zqg0.fsf@igalia.com> (raw)
In-Reply-To: <878ti3uzaz.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 29 Aug 2017 00:01:40 +0200")
On Tue 29 Aug 2017 00:01, ludo@gnu.org (Ludovic Courtès) writes:
> Yup, I just created a new ‘core-updates’ branch by pushing
> <https://bugs.gnu.org/27849>. Enjoy!
>
> Let’s freeze in one month, say Oct. 1st?
It would be pretty cool if we could fix our O(n^2) problems in search
paths in this core-updates -- basically whenever you go to create an
environment, instead of making e.g. VAR=A:B:C:..., for all VARs
(LIBRARY_PATH, PKG_CONFIG_PATH, etc), instead we make a union directory
Z containing the union of A, B, C, etc and set VAR=Z. The goal would be
to fix quadratic run-time lookup costs by replacing it with a
compile-time computation. This applies to many lookups: PATH, -rpath,
etc.
For specific variables we might also have to rewrite some internal
references, for example to replace the -L line in pkg-config files to
point to the union directory. Dunno if there are more examples or if
PKG_CONFIG_PATH is the only one.
Andy
next prev parent reply other threads:[~2017-08-29 9:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 22:01 ‘core-updates’ is back! Ludovic Courtès
2017-08-29 8:44 ` Efraim Flashner
2017-08-30 9:30 ` Efraim Flashner
2017-08-30 19:10 ` Marius Bakke
2017-08-30 20:16 ` Efraim Flashner
2017-08-30 20:37 ` Marius Bakke
2017-08-31 14:44 ` Ludovic Courtès
2017-08-31 16:23 ` Marius Bakke
2017-08-31 17:18 ` Marius Bakke
2017-09-02 11:18 ` Marius Bakke
2017-09-02 21:01 ` Ludovic Courtès
2017-08-30 21:17 ` Ricardo Wurmus
2017-08-30 21:51 ` Marius Bakke
2017-08-29 9:14 ` Andy Wingo [this message]
2017-08-29 10:01 ` Ricardo Wurmus
2017-08-29 13:36 ` 宋文武
2017-08-30 9:58 ` Ludovic Courtès
2017-08-30 9:58 ` Ludovic Courtès
2017-09-05 13:21 ` Ricardo Wurmus
2017-09-05 14:57 ` bug#26048: " 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=87val6zqg0.fsf@igalia.com \
--to=wingo@igalia.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 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).