On Wed, Jan 18 2017, 19:13:36 CET wrote Dale: > Howdy, Hi! > Looking to see how others do this. I noticed that some "system" stuff > was disabled which I assume means Seamonkey and Firefox would then > compile their own versions of those things or something. This is the > ones in question: > > system-harfbuzz > system-icu > system-jpeg > system-libevent > system-libvpx > system-sqlite > system-cairo > > Questions. How do you set yours and why if you know why? Which one is > most stable? Any other advantages to having it one way or the other. > Should some be on and others off?
I prefer to use system libs because upstream bundled libs are in nearly every
project now and then huge security risks (i.e. quite old libraries once(!)
imported from another project, slightly modified, never updated)[1].
However, I had to test a bit around which system-* flags don’t crash and
currently my setup contains firefox-50.0.1-r1::gentoo with
“system-harfbuzz system-icu system-jpeg system-libvpx system-sqlite“
and the rest needs to be used from bundled setups — at least that was the
state at firefox-49 and I didn’t really test more system-libs since then.
My system is ~amd64 on Haswell i5, SELinux no-multilib profile and systemd,
gcc-5.4.0-r2-hardened as compiler.
[1] Fun fact: spidermonkey seems to be the one anti example: bundled in 0ad is
always major versions ahead of what is on the mozilla overlay(sic!). These
poor guys need definetly assistance! :)
> Thanks.
Hope that helps,
Nils
> [...]
--
Nils Freydank
GnuPG-Key: 0x44594171807206CF @ hkp://keys.gnupg.net
fpr: AA2D 5CC0 0457 297F 6164 3911 4459 4171 8072 06CF
signature.asc
Description: This is a digitally signed message part.
