| 1 |
On Mon, Aug 01, 2016 at 10:21:20PM +0100, Mick wrote: |
| 2 |
> |
| 3 |
> I think libreoffice, chromium and firefox will be compiled in a chroot from now |
| 4 |
> on and then emerged as binaries. This is the difference for libreoffice: |
| 5 |
> |
| 6 |
> Sat Aug 29 06:09:09 2015 >>> app-office/libreoffice-4.4.4.3 |
| 7 |
> merge time: 15 hours, 34 minutes and 2 seconds. |
| 8 |
> |
| 9 |
> Sun Sep 13 01:36:03 2015 >>> app-office/libreoffice-4.4.5.2 |
| 10 |
> merge time: 15 hours, 13 minutes and 17 seconds. |
| 11 |
> |
| 12 |
> Sun Nov 29 02:30:04 2015 >>> app-office/libreoffice-5.0.3.2 |
| 13 |
> merge time: 16 hours, 54 minutes and 28 seconds. |
| 14 |
> |
| 15 |
> Sun Mar 27 09:31:20 2016 >>> app-office/libreoffice-5.0.5.2 |
| 16 |
> merge time: 17 hours and 8 seconds. |
| 17 |
> |
| 18 |
> Mon Aug 1 22:17:15 2016 >>> app-office/libreoffice-5.1.4.2 |
| 19 |
> merge time: 1 minute and 31 seconds. |
| 20 |
> |
| 21 |
> (chromium takes even longer!) :-) |
| 22 |
> |
| 23 |
|
| 24 |
Does it make sense to compile your own versions of these packages and then |
| 25 |
binary merge, when portage already contains binary ebuilds for these |
| 26 |
packages? (firefox-bin/libreoffice-bin/google-chrome) |
Archives