To me this seems much like an upstream problem, since the problem just
seems to be that xmonad isn't prepared to run without
~/.xmonad/xmonad.hs. I guess a proper fix would be to either let xmonad
create (and compile) a default configuration if it's missing or to run
with such a default configuration without writing it to a file, but
that's up to upstream.
We still need to keep in mind that, if upstream chooses to create a
standard configuration, xmonad needs to depend on libghc-xmonad-dev.
(Currently it just recommends it).

Joachim: Do you still think there is more info needed, or is the tag
just not removed?

Could someone report this on the upstream bugtracker? I myself don't
have a Google Code account and don't want to create one.

Regards
Sven

Attachment: signature.asc
Description: PGP signature

Reply via email to