| 1 |
On Thursday 02 Feb 2017 03:19:24 Dale wrote: |
| 2 |
> Nils Freydank wrote: |
| 3 |
> > On Wed, Jan 18 2017, 19:13:36 CET wrote Dale: |
| 4 |
> >> Howdy, |
| 5 |
> > |
| 6 |
> > Hi! |
| 7 |
> > |
| 8 |
> >> Looking to see how others do this. I noticed that some "system" stuff |
| 9 |
> >> was disabled which I assume means Seamonkey and Firefox would then |
| 10 |
> >> compile their own versions of those things or something. This is the |
| 11 |
> >> ones in question: |
| 12 |
> >> |
| 13 |
> >> system-harfbuzz |
| 14 |
> >> system-icu |
| 15 |
> >> system-jpeg |
| 16 |
> >> system-libevent |
| 17 |
> >> system-libvpx |
| 18 |
> >> system-sqlite |
| 19 |
> >> system-cairo |
| 20 |
> >> |
| 21 |
> >> Questions. How do you set yours and why if you know why? Which one is |
| 22 |
> >> most stable? Any other advantages to having it one way or the other. |
| 23 |
> >> Should some be on and others off? |
| 24 |
> > |
| 25 |
> > I prefer to use system libs because upstream bundled libs are in nearly |
| 26 |
> > every project now and then huge security risks (i.e. quite old libraries |
| 27 |
> > once(!) imported from another project, slightly modified, never |
| 28 |
> > updated)[1]. |
| 29 |
> > |
| 30 |
> > However, I had to test a bit around which system-* flags don’t crash and |
| 31 |
> > currently my setup contains firefox-50.0.1-r1::gentoo with |
| 32 |
> > |
| 33 |
> > “system-harfbuzz system-icu system-jpeg system-libvpx system-sqlite“ |
| 34 |
> > |
| 35 |
> > and the rest needs to be used from bundled setups — at least that was the |
| 36 |
> > state at firefox-49 and I didn’t really test more system-libs since then. |
| 37 |
> > My system is ~amd64 on Haswell i5, SELinux no-multilib profile and |
| 38 |
> > systemd, |
| 39 |
> > gcc-5.4.0-r2-hardened as compiler. |
| 40 |
> > |
| 41 |
> > [1] Fun fact: spidermonkey seems to be the one anti example: bundled in |
| 42 |
> > 0ad is always major versions ahead of what is on the mozilla |
| 43 |
> > overlay(sic!). These poor guys need definetly assistance! :) |
| 44 |
> > |
| 45 |
> >> Thanks. |
| 46 |
> > |
| 47 |
> > Hope that helps, |
| 48 |
> > Nils |
| 49 |
> > |
| 50 |
> >> [...] |
| 51 |
> |
| 52 |
> I been using system libs since just before my first post. So far, it's |
| 53 |
> working pretty well. No crashes or anything. I also upgraded Firefox |
| 54 |
> the other day when it did its release. It built and seems to be running |
| 55 |
> fine. When it breaks or stops working right, I'll try switching back. |
| 56 |
> |
| 57 |
> Thanks to all for the replies. I was curious what others were doing. |
| 58 |
> It seems others use both ways for differing reasons. |
| 59 |
> |
| 60 |
> Dale |
| 61 |
> |
| 62 |
> :-) :-) |
| 63 |
|
| 64 |
Other than security implications of older libs being built in with default USE |
| 65 |
flags, is there some performance or emerge time benefit/disbenefit from using |
| 66 |
system-libs? |
| 67 |
-- |
| 68 |
Regards, |
| 69 |
Mick |
Archives