From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] make PORTAGE_BIN_PATH settings relocatable
Date: Tue, 2 Jun 2015 11:34:19 -0400 [thread overview]
Message-ID: <20150602153419.GE23039@vapier> (raw)
In-Reply-To: <556CA924.6010406@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
On 01 Jun 2015 11:49, Zac Medico wrote:
> On 06/01/2015 10:25 AM, Mike Frysinger wrote:
> > (a) just throw an error and exit when PORTAGE_BIN_PATH is not set ...
> > considering the current portage code points to a path where it is no longer
> > installed, maybe that's ok ? the recent changes to make portage install copies
> > for each python version is what broke it i think.
>
> I like this idea. I can't think of a reason why we should allow
> PORTAGE_BIN_PATH to be unset.
i'll try this in the CrOS project where we're using Gentoo/Prefix and see how it
goes. and then try it on my system for a while to further check it. otherwise
i'll go with Tim's inspired idea about symlinked wrappers.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-02 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 6:34 [gentoo-portage-dev] [PATCH] make PORTAGE_BIN_PATH settings relocatable Mike Frysinger
2015-06-01 17:25 ` Mike Frysinger
2015-06-01 18:01 ` Tim Harder
2015-06-02 4:31 ` Mike Frysinger
2015-06-02 5:27 ` Tim Harder
2015-06-01 18:49 ` Zac Medico
2015-06-02 15:34 ` Mike Frysinger [this message]
2015-06-10 15:45 ` [gentoo-portage-dev] [PATCH] require PORTAGE_{BIN,PYM}_PATH not be cleared Mike Frysinger
2015-06-10 18:31 ` Zac Medico
2015-06-11 6:44 ` Brian Dolbec
2015-06-11 9:57 ` Mike Frysinger
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=20150602153419.GE23039@vapier \
--to=vapier@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.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