On Fri, 2008-12-19 at 15:23 -0500, Yaakov Nemoy wrote:
2008/12/19 Matthias Clasen <mclasen(a)redhat.com>:
> On Thu, 2008-12-18 at 08:23 -0500, Matthias Clasen wrote:
>> On Thu, 2008-12-18 at 02:19 -0500, Yaakov Nemoy wrote:
>> >
>> > In short, the new gnome session configuration dialog is alot simpler
>> > and alot less confusing, but it gives us no simple way to give
>> > metacity the boot on a per session basis. How do i go about doing
>> > this via an RPM?
>>
>> The required components should just be a fallback in case the session
>> didn't contain a window manager, file manager, etc. At least that is my
>> understanding of how they're supposed to be used. So, you should just
>> install an autostart file for xmonad that marks it as a window manager
>> via
>>
>> X-GNOME-Autostart-Phase=WindowManager
>> X-GNOME-Provides=windowmanager
>>
>> then your users should be able to switch their sessions to xmonad by
>> turning it on in the session capplet.
>
> Just tried this with openbox, and it works fine.
At this point, i don't care about openbox. Openbox complies with
certain standards that the xmonad devs decided are a waste of lines of
code. All i'm looking to do is convince gnome that it doesn't need a
window manager at all. In the older versions of gnome, metacity
showed up as just yet another app in the sessions-capplet. Not
anymore.
I just tried it with openbox. If you do the same with xnomad, it will
work too. metacity doesn't show up in the session-capplet because it
doesn't install an autostart file, because gnome-session runs it as the
fallback to ensure that the required component 'windowmanager' is
present in the session.