From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gnome intrusion?
Date: Tue, 15 Nov 2016 21:10:32 -0500 [thread overview]
Message-ID: <20161116021032.GA20819@waltdnes.org> (raw)
In-Reply-To: <CAKpSnpLhqqnkHFYqUw=te-yG6s1v8dsi7pc8Vhj4UFbB_pdrnQ@mail.gmail.com>
On Mon, Nov 14, 2016 at 11:52:50PM +0000, Jorge Almeida wrote
> Good to know. I'm currently testing openbox without dbus-launch. No
> problem yet.
>
> It would be great to have some WiKi pages telling what some USE flag
> really do to particular packages, e.g, what does it mean to run
> firefox without dbus.
The current Pale Moon requires glib-dbus. I do my own custom builds
of Pale Moon for my personal use without dbus. I also have an ancient
32-bit-only Atom netbook. dbus is required for Necko-Wifi and Wakelock
in Pale Moon, and presumably also in Firefox...
Necko-Wifi - allows improved geo-location if you have wifi, which most
PCs have, even newer desktops. It works by scanning SSIDs in your
vicinity and comparing against a master global database. The local data
has to be sent off to a master database (e.g. Google) for the comparison.
Wakelock - is a generic API for grabbing a resource and not letting go
of it... https://www.w3.org/TR/wake-lock-use-cases/ It's mostly used
in mobile apps, but on the desktop it's used to disable the screensaver
while a long video is playing.
If you can do without Necko-Wifi and Wakelock, you don't need dbus.
Let me know off-list if you need any help custom-building Pale Moon.
You can also join the Pale Moon web forum https://forum.palemoon.org/
The linux section is https://forum.palemoon.org/viewforum.php?f=37
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2016-11-16 2:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 9:32 [gentoo-user] gnome intrusion? Jorge Almeida
2016-11-14 17:37 ` [gentoo-user] " Ian Zimmerman
2016-11-14 19:03 ` Jorge Almeida
2016-11-14 20:37 ` Kai Krakow
2016-11-14 21:49 ` Jorge Almeida
2016-11-14 23:51 ` Kai Krakow
2016-11-16 12:47 ` [gentoo-user] sans-dbus was: " Miroslav Rovis
2016-11-16 18:42 ` Jorge Almeida
2016-11-17 1:48 ` Rich Freeman
2016-11-17 7:56 ` [gentoo-user] " Ian Zimmerman
2016-11-17 9:08 ` Rich Freeman
2016-11-19 9:21 ` Kai Krakow
2016-11-19 19:06 ` Ian Zimmerman
2016-11-19 19:16 ` Rich Freeman
2016-11-19 20:47 ` Ian Zimmerman
2016-11-19 21:07 ` Alan McKinnon
2016-11-19 21:23 ` Ian Zimmerman
2016-11-19 22:34 ` Canek Peláez Valdés
2016-11-19 22:36 ` Alan McKinnon
2016-11-20 0:36 ` Walter Dnes
2016-11-19 21:59 ` [gentoo-user] " Tom H
2016-11-19 22:15 ` Rich Freeman
2016-11-20 18:40 ` [gentoo-user] " Kai Krakow
2016-11-14 23:38 ` [gentoo-user] " Andrew Tselischev
2016-11-14 23:52 ` Jorge Almeida
2016-11-15 17:39 ` [gentoo-user] " Ian Zimmerman
2016-11-15 19:23 ` Jorge Almeida
2016-11-15 19:32 ` Alan McKinnon
2016-11-15 19:45 ` Jorge Almeida
2016-11-16 2:10 ` Walter Dnes [this message]
2016-11-16 7:23 ` [gentoo-user] " Jorge Almeida
2016-11-16 9:08 ` Neil Bothwick
2016-11-16 11:25 ` Jorge Almeida
2016-11-16 20:51 ` [gentoo-user] " Kai Krakow
2016-11-16 21:20 ` Jorge Almeida
2016-11-17 20:42 ` [gentoo-user] " Frank Steinmetzger
2016-11-17 20:49 ` Jorge Almeida
2016-11-17 23:32 ` Frank Steinmetzger
2016-11-14 23:55 ` [gentoo-user] " Kai Krakow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161116021032.GA20819@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox