1 |
Hi James, |
2 |
|
3 |
thank you for your reply. |
4 |
|
5 |
On Sat, Sep 26, 2015 at 02:08:19PM +0000, James wrote: |
6 |
> I have been following 'bcache' as an interesting addition to complex |
7 |
> compiling scenarios. I'm not certain how it will help your 'wild ideas', |
8 |
> but it is worth a look, imho |
9 |
|
10 |
Yes, I have also heard of bcachefs, but unless I am terribly mistaken, it |
11 |
doesn't offer me anything to solve my actual problem, which is "setting |
12 |
portage environment variables according to MERGE_TYPE". |
13 |
|
14 |
I am aware that my setup might not be ideal and that approaches like bcachefs |
15 |
might help me creating a better compile-install-workflow. But for now -- just |
16 |
for the fun of it -- let's assume that the underlying basis is fixed and all |
17 |
that is left is finding a way to dynamically change variables like |
18 |
PORTAGE_TMPDIR. |
19 |
|
20 |
That could also be used for scenarios like "if the package needs to be |
21 |
compiled, then use every single machine in the local network as a distcc |
22 |
server; if there is already a tbz2 file for the given package, then just |
23 |
install it without searching for potential servers". |
24 |
|
25 |
Portage's bashrc can be a powerful script for several use-cases, but at the |
26 |
moment I am quite sad that I can't change environment variables in there. |
27 |
|
28 |
So, any other ideas? |
29 |
|
30 |
Regards, |
31 |
--Flo |