| 1 |
On 2018.12.04 20:36, Adam Carter wrote: |
| 2 |
> On Wed, Dec 5, 2018 at 7:41 AM Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
> |
| 4 |
> > On Tuesday, 4 December 2018 19:23:27 GMT Jack wrote: |
| 5 |
> > Phew! The chromium emerge completed with -j1, although it took 4 |
| 6 |
> hours |
| 7 |
> > longer |
| 8 |
> > than last time on one PC and 6.5 hours longer on another. |
| 9 |
> > |
| 10 |
> |
| 11 |
> For those systems it might be worth trying the binary google-chrome |
| 12 |
> instead. Much smaller download and; |
| 13 |
> |
| 14 |
> $ genlop -t google-chrome | tail -n3 |
| 15 |
> Tue Nov 20 20:20:10 2018 >>> |
| 16 |
> www-client/google-chrome-70.0.3538.110 |
| 17 |
> merge time: 35 seconds. |
| 18 |
> |
| 19 |
But only if you don't care about the differences between Chrome and |
| 20 |
Chromium. They are close, but not (unless I'm terribly mistaken) |
| 21 |
exactly the same. The latter is completely FOSS, but the former |
| 22 |
contains some Google specific additions. While I do have both |
| 23 |
installed, I don't particularly trust Google enough to use Chrome |
| 24 |
unless nothing else works. It's pretty rare I need to use it. |
| 25 |
|
| 26 |
Jack |
Archives