| 1 |
On 4/30/12 6:32 PM, Matt Turner wrote: |
| 2 |
> On Mon, Apr 30, 2012 at 12:11 PM, Mike Frysinger <vapier@g.o> wrote: |
| 3 |
>> On Monday 30 April 2012 12:00:59 Rich Freeman wrote: |
| 4 |
>>> doing it wrong. I don't like how Google develops Android in the dark, |
| 5 |
>>> or that they bundle 1GB of third-party stuff in their Chromium source |
| 6 |
>>> and distribute a favored binary-only derivative. |
| 7 |
>> |
| 8 |
>> err, they distribute a Chromium source tarball, and their build system |
| 9 |
>> includes flags to use the system versions of those bundled libs if you so |
| 10 |
>> choose. i think this is a perfectly fine compromise. |
| 11 |
|
| 12 |
Right, and the source tarball is ~175 MB. It's not perfect, but it's |
| 13 |
also far from 1 GB. The bundled libraries are included in the tarball. |
| 14 |
|
| 15 |
> It looks like chromium-20.0.1115.1.ebuild removes 45 bundled |
| 16 |
> libraries. |
| 17 |
|
| 18 |
Note that the list in the ebuild is about _excluding_ bundled libraries, |
| 19 |
i.e. the directories listed are removed and everything else is removed. |
| 20 |
|
| 21 |
I'm generally co-operating with upstream (also as part of that upstream, |
| 22 |
but with limited resources at least for now) so that there are options |
| 23 |
to use system libraries, and what's left is non-trivial to unbundle |
| 24 |
(e.g. mesa) but it should be unbundled at some point. |
| 25 |
|
| 26 |
> and still has TODOs in place to use the system's ffmpeg, |
| 27 |
> hunspell, (Open?)SSL, SQLite, and libvpx. |
| 28 |
|
| 29 |
Yes, the TODOs can definitely tell you what's left there. The list is |
| 30 |
not comprehensive though. |
| 31 |
|
| 32 |
Ah, and help is always welcome - with unbundling libraries, gcc-4.7 |
| 33 |
porting, and other things. Feel free to send your thoughts/questions to |
| 34 |
chromium@g.o. |
| 35 |
|
| 36 |
Paweł |
Archives