From: "Florian Gamböck" <ml@floga.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dynamically change PORTAGE_TMPDIR via bashrc?
Date: Sun, 27 Sep 2015 15:13:52 +0200 [thread overview]
Message-ID: <20150927131352.GA11081@lira> (raw)
In-Reply-To: <loom.20150926T160545-925@post.gmane.org>
Hi James,
thank you for your reply.
On Sat, Sep 26, 2015 at 02:08:19PM +0000, James wrote:
> I have been following 'bcache' as an interesting addition to complex
> compiling scenarios. I'm not certain how it will help your 'wild ideas',
> but it is worth a look, imho
Yes, I have also heard of bcachefs, but unless I am terribly mistaken, it
doesn't offer me anything to solve my actual problem, which is "setting
portage environment variables according to MERGE_TYPE".
I am aware that my setup might not be ideal and that approaches like bcachefs
might help me creating a better compile-install-workflow. But for now -- just
for the fun of it -- let's assume that the underlying basis is fixed and all
that is left is finding a way to dynamically change variables like
PORTAGE_TMPDIR.
That could also be used for scenarios like "if the package needs to be
compiled, then use every single machine in the local network as a distcc
server; if there is already a tbz2 file for the given package, then just
install it without searching for potential servers".
Portage's bashrc can be a powerful script for several use-cases, but at the
moment I am quite sad that I can't change environment variables in there.
So, any other ideas?
Regards,
--Flo
prev parent reply other threads:[~2015-09-27 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 8:08 [gentoo-user] Dynamically change PORTAGE_TMPDIR via bashrc? Florian Gamböck
2015-09-26 14:08 ` [gentoo-user] " James
2015-09-26 15:21 ` Rich Freeman
2015-09-26 16:35 ` James
2015-09-27 13:13 ` Florian Gamböck [this message]
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=20150927131352.GA11081@lira \
--to=ml@floga.de \
--cc=gentoo-user@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