1 |
On 18/12/2014 03:33, Alec Ten Harmsel wrote: |
2 |
> |
3 |
> On 12/17/2014 04:59 PM, Alan McKinnon wrote: |
4 |
>> On 18/12/2014 04:45, Harry Putnam wrote: |
5 |
>>> Is there any advantage one way or the other emerging firefox.bin vs firefox? |
6 |
>> Depends on your needs: |
7 |
>> |
8 |
>> firefox: |
9 |
>> - pro: you get all the USE flags |
10 |
>> - pro: you don't get bundled libs from Mozilla, the ebuild can use |
11 |
>> system libs |
12 |
>> - pro: the compiled binaries are integrated into gentoo like other ebuilds |
13 |
>> - con: slow compiles. I have 8 i7 cores and 16G. the merge takes 20-35 |
14 |
>> minutes... |
15 |
> |
16 |
> Really? 20-35 minutes? I have 6 cores and 32G, and firefox only takes 10 |
17 |
> minutes. Do you have PORTAGE_TMPDIR mounted on tmpfs? |
18 |
|
19 |
|
20 |
|
21 |
Yes, it is a tmpfs. I notice firefox compile times have been steadily |
22 |
increasing over time, and also vary a lot. But, with 16G ram, I've |
23 |
stopped worrying about what else the machine is doing when emerging. |
24 |
I'll easily do an mp4 encode with handbrake while building firefox and |
25 |
not worry about load :-) |
26 |
|
27 |
Sat Aug 2 14:08:00 2014 >>> www-client/firefox-31.0 |
28 |
merge time: 18 minutes and 37 seconds. |
29 |
|
30 |
Mon Sep 1 00:08:02 2014 >>> www-client/firefox-31.0 |
31 |
merge time: 13 hours, 54 minutes and 44 seconds. |
32 |
|
33 |
Thu Sep 4 23:53:39 2014 >>> www-client/firefox-32.0 |
34 |
merge time: 19 minutes and 50 seconds. |
35 |
|
36 |
Sun Sep 14 10:43:15 2014 >>> www-client/firefox-32.0 |
37 |
merge time: 41 minutes and 59 seconds. |
38 |
|
39 |
Thu Oct 16 19:50:24 2014 >>> www-client/firefox-33.0 |
40 |
merge time: 34 minutes and 56 seconds. |
41 |
|
42 |
Fri Nov 7 20:34:48 2014 >>> www-client/firefox-33.0-r1 |
43 |
merge time: 21 minutes and 13 seconds. |
44 |
|
45 |
Sun Dec 7 14:01:03 2014 >>> www-client/firefox-34.0.5-r1 |
46 |
merge time: 37 minutes and 31 seconds. |
47 |
|
48 |
|
49 |
|
50 |
-- |
51 |
Alan McKinnon |
52 |
alan.mckinnon@×××××.com |