From: Jorge Almeida <jjalmeida@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sans-dbus was: gnome intrusion?
Date: Wed, 16 Nov 2016 18:42:34 +0000 [thread overview]
Message-ID: <CAKpSnp+QFEgAFk-R1ta75WtFQFKgEzjm1b7t++Q2S5fgdiKNSw@mail.gmail.com> (raw)
In-Reply-To: <20161116124726.GA8424@g0n.xdwgrp>
On Wed, Nov 16, 2016 at 12:47 PM, Miroslav Rovis
<miro.rovis@croatiafidelis.hr> wrote:
> On 161114-21:49+0000, Jorge Almeida wrote:
> I live without dbus. I've only recently noticed (can't be since long)
> there is a dbus flag.
>
I knew Gentoo doesn't force the use of dbus, but I had the flag set,
since I expected assorted breakages. For example, when viewing a pdf
file, will updating the view when the file changes be possible without
dbus? This is the kind of trouble I expect. Not the fault of Gentoo,
anyway.
As for the *kit stuff, I just don't have it. It's safe to do without
that stuff, as far as I can tell.
>
> Also, I've noticed that our developers are lending an ear to sans-dbus
> users, as they are getting way more packages then previosly that do not
> depend in the least on dbus anymore (Firefox, Wireshark, Inkscape ...
> well I don't use very many packages... Ah, not to forget, Qt5 now does
> not depend on dbus, or D-Bus, used below...)
>
Yes. A couple of weeks ago, I needed alpine, which tried to pull PAM.
The current ebuild already has PAM as an option, which is fine
(didn't emerge it yet, though). So, it seems some packages have hard
dependencies just because developers assumed "everybody uses it" or
"nobody will mind", not due to some dark agenda.
For my needs, Gentoo is the best distro out there. (Until recently, I
used Slackware, as well as Gentoo. Had to give up on Slackware 14.2,
with regret. Because pulseaudio,)
Regards,
Jorge
next prev parent reply other threads:[~2016-11-16 18:43 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 [this message]
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 ` [gentoo-user] " Walter Dnes
2016-11-16 7:23 ` 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=CAKpSnp+QFEgAFk-R1ta75WtFQFKgEzjm1b7t++Q2S5fgdiKNSw@mail.gmail.com \
--to=jjalmeida@gmail.com \
--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