In F16 gdm requires gnome-settings-daemon which requires PackageKit-glib which indirectly requires yum. That gives an unfortunate and long dependency chain for live CDs. Could you please break that chain?
I don't know how the chain could be broken. Do gdm really need gnome-settings-daemon?
Alternatively, if it has to be reassigned to gnome-settigns-daemon: Could PackageKit be an optional plugin to gnome-settings-daemon instead of a mandatory dependency?
gdm definitely needs gnome-settings-daemon.
I could see an argument for PackageKit not requiring yum since it supports multiple backends, and I could see an argument for gnome-settings-daemon having a subpackage for optional plugins.
Certainly for one-off-special-purpose spins I could imagine not wanting yum. It's hard for me to imagine wanting gdm in those scenarios either though.
(In reply to comment #1)
> Certainly for one-off-special-purpose spins I could imagine not wanting yum.
> It's hard for me to imagine wanting gdm in those scenarios either though.
Agreed. Many/most spins don't "want" gdm but include it (by dependencies?) and just configure it to autologin. That is also a waste of resources.
It was my impression that gdm also did something extra that was important and wasn't easy to live without - and apparently no other spinners has tried and succeeded in creating a spin without gdm. Can you give a hint how gdm can be bypassed completely? Is it just a matter of hacking display-manager.service or prefdm to exec gnome-session like Xsession does?
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.