On Saturday 10 Dec 2016 00:22:19 Daniel Campbell wrote:
> On 12/10/2016 12:10 AM, Mick wrote:
> > Hi All,
> > 
> > I have set up USE="-gnome" in my make.conf, but I saw this cropping up at
> > my latest emerge --update:
> > 
> > [ebuild   R    ] media-sound/pulseaudio-9.0::gentoo  USE="X alsa
> > alsa-plugin asyncns bluetooth caps dbus gdbm glib gnome* ipv6 orc qt4 ssl
> > tcpd udev webrtc-aec -doc -equalizer -gtk -jack (-libressl)
> > -libsamplerate -lirc - native-headset (-neon) -ofono-headset (-oss)
> > -realtime (-selinux) -sox (- system-wide) -systemd {-test} -xen
> > -zeroconf" ABI_X86="32 (64) (-x32)" 0 KiB [snip...]
> > 
> > Total: 127 packages (83 upgrades, 3 new, 41 reinstalls), Size of
> > downloads:
> > 268,203 KiB
> > 
> > The following USE changes are necessary to proceed:
> >  (see "package.use" in the portage(5) man page for more details)
> > 
> > # required by kde-plasma/plasma-pa-5.8.3::gentoo
> > # required by kde-plasma/plasma-meta-5.8.3::gentoo[pulseaudio]
> > # required by kde-apps/kdebase-meta-16.04.3::gentoo
> > # required by @selected
> > # required by @world (argument)
> > 
> >> =media-sound/pulseaudio-9.0 gnome
> > 
> > which is dragging in gconf:
> > 
> > [ebuild  N     ] gnome-base/gconf-3.2.6-r4:2::gentoo  USE="introspection
> > ldap (policykit) -debug" ABI_X86="(64) -32 (-x32)"
> > PYTHON_TARGETS="python2_7" 0 KiB
> > 
> > 
> > I don't see gnome in REQUIRED_USE and since this is a relatively
> > gnome-free PC I was wondering what's causing the above and if I can avoid
> > gconf?
> > 
> > PS:  euse -i gnome shows:
> > 
> > [- c    ] gnome
> > 
> >     media-sound/pulseaudio: Use GConf to store user preferences on
> >     streams and so on. Don't enable this flag if you want to use a system
> >     wide instance. If unsure, enable this flag.
> >     
> >         [-  ] 7.1 [gentoo]
> >         [-  ] 8.0 [gentoo]
> >         [-  ] 9.0 [gentoo]
> 
> When portage suggests a USE change due to a blocker, the "culprits" are
> listed from "smallest" to "largest". So in this case,
> kde-plasma/plasma-pa is the culprit: a quick `less $(equery w
> plasma-pa)` shows that plasma-pa is depending on gconf and
> pulseaudio[gnome].
> 
> If upstream has decided to depend on gconf, it makes perfect sense to
> depend on PA with the 'gnome' USE flag. This is probably so plasma can
> correctly run as a user and keep track of file/sound settings.
> 
> The KDE team can likely explain *why* this change happened, though you
> might want to check the homepage for plasma-pa first. The KDE team can
> be reached via the mail alias (kde@g.o) or on Freenode via #gentoo-kde.
> 
> I hope this helps clear things up for you.
> 
> ~zlg

Yes, thank you Daniel and Marc.  The bug explains why the devs chose adding 
gconf.  I don't think this is necessary on a PC with a single audio sink and 
could have been left out, but then you could argue pulseaudio itself is 
optional.
-- 
Regards,
Mick

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to