From: "Ludovic Courtès" <ludo@gnu.org>
To: 25422@debbugs.gnu.org
Subject: bug#25422: [PATCH 0/2] Support single-entry search paths
Date: Sun, 22 Jan 2017 22:51:59 +0100 [thread overview]
Message-ID: <20170122215201.7948-1-ludo@gnu.org> (raw)
In-Reply-To: <87h951jq2s.fsf@gnu.org>
Hi!
These patches for ‘core-updates’ add support for “single-entry” search
paths like ‘GIT_SSL_CAINFO’. This is achieved by setting ‘separator’ to
#f in the search path spec.
Feedback welcome!
Ludo’.
Ludovic Courtès (2):
guix package: Honor the order of profiles when -p appears multiple
times.
search-paths: Allow specs with #f as their separator.
Makefile.am | 3 ++-
gnu/packages/version-control.scm | 4 ++--
guix/build/profiles.scm | 24 ++++++++++++--------
guix/build/utils.scm | 13 ++++++++---
guix/scripts/package.scm | 4 ++--
guix/search-paths.scm | 28 ++++++++++++++++-------
tests/guix-package-net.sh | 4 ++--
tests/packages.scm | 49 +++++++++++++++++++++++++++++++++++++++-
tests/search-paths.scm | 48 +++++++++++++++++++++++++++++++++++++++
9 files changed, 148 insertions(+), 29 deletions(-)
create mode 100644 tests/search-paths.scm
--
2.11.0
next prev parent reply other threads:[~2017-01-22 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 20:36 bug#25422: GIT_SSL_CAINFO set incorrectly Leo Famulari
2017-01-14 21:20 ` Ludovic Courtès
2017-01-22 21:51 ` Ludovic Courtès [this message]
2017-01-22 21:52 ` bug#25422: [PATCH 1/2] guix package: Honor the order of profiles when -p appears multiple times Ludovic Courtès
2017-01-22 21:52 ` bug#25422: [PATCH 2/2] search-paths: Allow specs with #f as their separator Ludovic Courtès
2017-01-23 13:00 ` bug#25422: [PATCH 0/2] Support single-entry search paths Ricardo Wurmus
2017-01-23 22:02 ` Ludovic Courtès
2017-04-02 22:22 ` Ludovic Courtès
2017-01-20 4:27 ` bug#25422: GIT_SSL_CAINFO set incorrectly Mekeor Melire
2017-01-23 13:57 ` Ludovic Courtès
2017-02-10 16:22 ` Mekeor Melire
2017-02-10 20:51 ` 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=20170122215201.7948-1-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=25422@debbugs.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).