From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Revert "xbps-src/chroot.sh: sanitize PATH."
Date: Sun, 07 Jul 2019 09:15:41 +0200 [thread overview]
Message-ID: <20190707071541.iyCeW9iKtFFzxL7UUM6a7_vPyQTa-qDnxyRuQBld6qw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12875@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/12875#issuecomment-508977224
Comment:
in my `xbps-src-ultra-fast` branch:
```
#
# Sanitize PATH.
#
if [ -z "$IN_CHROOT" ]; then
# In non chroot case always prefer host tools.
export PATH="$PATH:$XBPS_MASTERDIR/usr/bin"
fi
```
This should be even picking up your xbps tools at /usr/local/bin as long as your PATH is ok.
next prev parent reply other threads:[~2019-07-07 7:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 6:58 [PR PATCH] " voidlinux-github
2019-07-07 6:59 ` voidlinux-github
2019-07-07 7:02 ` voidlinux-github
2019-07-07 7:04 ` voidlinux-github
2019-07-07 7:05 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-07 7:05 ` voidlinux-github
2019-07-07 7:06 ` voidlinux-github
2019-07-07 7:07 ` voidlinux-github
2019-07-07 7:07 ` voidlinux-github
2019-07-07 7:07 ` voidlinux-github
2019-07-07 7:08 ` voidlinux-github
2019-07-07 7:08 ` voidlinux-github
2019-07-07 7:10 ` voidlinux-github
2019-07-07 7:11 ` voidlinux-github
2019-07-07 7:12 ` voidlinux-github
2019-07-07 7:13 ` voidlinux-github
2019-07-07 7:15 ` voidlinux-github [this message]
2019-07-07 7:17 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-07 7:17 ` voidlinux-github
2019-07-07 7:19 ` voidlinux-github
2019-07-07 7:19 ` voidlinux-github
2019-07-07 7:21 ` voidlinux-github
2019-07-07 7:23 ` voidlinux-github
2019-07-07 7:23 ` voidlinux-github
2019-07-07 7:27 ` voidlinux-github
2019-07-07 7:28 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190707071541.iyCeW9iKtFFzxL7UUM6a7_vPyQTa-qDnxyRuQBld6qw@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).