Bug 522998 - remove libcanberra-gtk2 dependency on gdm
Summary: remove libcanberra-gtk2 dependency on gdm
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libcanberra
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Target
TreeView+ depends on / blocked
 
Reported: 2009-09-13 07:42 UTC by Daniel Mach
Modified: 2014-05-14 09:09 UTC (History)
9 users (show)

Fixed In Version: 0.17-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-16 22:22:46 UTC
Type: ---


Attachments (Terms of Use)

Description Daniel Mach 2009-09-13 07:42:37 UTC
I have a KDE desktop and I don't want to install gdm (I use kdm instead).
When I exclude it from yum update, I get this:
  --> Missing Dependency: gdm is needed by package libcanberra-gtk2-0.17-1.fc12.i686 (rawhide)

Is it possible to remove this dependency?
I don't see any reason why a sound library would require a login manager.

Comment 1 Lennart Poettering 2009-09-13 20:26:01 UTC
libcanberra-gtk2 places some files in directories created by the gdm package such as /usr/share/gdm/autostart/LoginWindow/. It thus needs to pull in gdm.

Comment 2 Matthias Clasen 2009-09-14 00:51:18 UTC
This might be a case where duplicate ownership for the directory is appropriate.

Comment 3 Daniel Mach 2009-09-15 10:50:53 UTC
Can you split it to a new subpackage libcanberra-gdm?
That would solve the problem.

Comment 4 Marcela Mašláňová 2009-09-15 10:55:40 UTC
I wonder why I need gdm and another dependent packages. I removed gdm with all new dependencies and sound works.

libcanberra-gtk2
pulseaudio-gdm-hooks

These requieres doesn't make sense to me. Who requires these two and why they were installed when I don't need them?

Comment 5 Sebastian Vahl 2009-09-15 14:28:59 UTC
This newly introduced dependency on gdm will also pull some unneeded gnome packages into the KDE live images (which will increase the size by ~30 megs). So please use a duplicate ownership or a subpackage for this.

Comment 6 Kevin Kofler 2009-09-15 14:40:51 UTC
+1, requiring a display manager in an application-level library just doesn't make sense from a logical perspective and it bloats the KDE Live image (as gdm in turn directly or indirectly drags in a lot of other GNOME stuff and even xulrunner), those directories really need to be co-owned in this case.

(The reason libcanberra-gtk2 ends up on the KDE live image in the first place is that firstboot requires metacity which requires libcanberra-gtk2. We also still ship pavucontrol which also requires libcanberra-gtk2, but that one could be dropped, firstboot can't. ;-) )

Comment 7 Lennart Poettering 2009-09-15 23:06:48 UTC
If someone of our KDE-loving friends wants to split off  /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop into a seperate package libcanberra-gdm-hooks that is pulled in by gdm he's welcome to do that. I am not the only one with commit access to gdm/libcanberra's rpm cvs.

Comment 8 Kevin Kofler 2009-09-16 00:28:33 UTC
So you prefer a subpackage for just the one file rather than just having libcanberra-gtk2 own the /usr/share/gdm/autostart/LoginWindow/ hierarchy together with gdm? I can easily implement that (the subpackage) if that's how you want things done.

Comment 9 Kevin Kofler 2009-09-16 00:30:08 UTC
(Be warned that the dependency will be circular though: libcanberra-gdm-hooks requiring gdm for directory ownership and gdm requiring libcanberra-gdm-hooks because something has to and it can't be libcanberra-gtk2 because then it'd be dragging in gdm again.)

Comment 10 Bill Nottingham 2009-09-16 03:27:00 UTC
.... just own the directory. Simplest answers are best.

Comment 11 Kevin Kofler 2009-09-16 22:15:55 UTC
* Wed Sep 16 2009 Kevin Kofler <Kevin.org> 0.17-2
- Don't require gdm in -gtk2 (#522998)

Comment 12 Lennart Poettering 2009-09-17 02:51:32 UTC
(In reply to comment #10)
> .... just own the directory. Simplest answers are best.  

Which is not really what the policy says... (Unless your proposal geoes through of course)


Note You need to log in before you can comment on or make changes to this bug.