Hi,
Am Samstag, den 20.09.2014, 22:35 +0200 schrieb Sven Bartscher: > 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. well, it used to be the case that xmonad would run happily without ~/.xmonad/xmonad.hs, and I’m surprised that it is not the case any more. Sven, did you reproduce the problem already? I didn’t find the time (which involves things like logging out :-)) yet. > 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). Upstream provides a standard configuration, it’s what’s compiled into /usr/bin/xmonad. > Joachim: Do you still think there is more info needed, or is the tag > just not removed? We need to reproduce the problem first, and be sure that it is not Debian specific in any way. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
