| 1 |
On Wed, Mar 04, 2020 at 07:12:35PM +0100, n952162 wrote |
| 2 |
> On 2020-03-04 17:14, Daniel Frey wrote: |
| 3 |
> > |
| 4 |
> > It will go away but allowing Firefox to self-update on Gentoo will get |
| 5 |
> > you a very broken Firefox as the ebuilds have gone away from large |
| 6 |
> > monolithic builds to linking to local system libraries. Not recommended! |
| 7 |
> > |
| 8 |
> > Dan |
| 9 |
> > |
| 10 |
> |
| 11 |
> Ah, good point. But I should be able to do the same thing from with |
| 12 |
> "preference" somewhere, I suspect. |
| 13 |
|
| 14 |
A Pale Moon user here. We get the same warnings about not building |
| 15 |
Pale Moon with system libs (item 5 |
| 16 |
https://forum.palemoon.org/viewtopic.php?f=62&t=20885 ). Since PM is a |
| 17 |
Firefox fork, it inherits a lot of the same behaviour. I notice that |
| 18 |
doing "emerge -pv firefox" shows the following default USE flags... |
| 19 |
|
| 20 |
system-av1 system-harfbuzz system-icu system-jpeg system-libevent |
| 21 |
system-libvpx system-sqlite system-webp |
| 22 |
|
| 23 |
Over-riding them in package.use, that should prevent the problems. |
| 24 |
|
| 25 |
-- |
| 26 |
Walter Dnes <waltdnes@××××××××.org> |
| 27 |
I don't run "desktop environments"; I run useful applications |
Archives