guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 12/13] gnu: Add xmonad.


From: Siniša Biđin
Subject: Re: [PATCH 12/13] gnu: Add xmonad.
Date: Mon, 24 Aug 2015 05:00:03 +0200

On 2015-08-23 22:47, Eric Bavier wrote:
I had to replace "Exec=/etc/X11/Session/xmonad" with "Exec=xmonad"
in this xmonad.desktop file in order to launch an xmonad session from
Slim.  Does this seem right?

Definitely!

I didn't test it thoroughly enough: I've been running xmonad via an
xsession file and managed to accidentally avoid the issue.

Does it make sense to fetch this file
from gentoo.org and then modify it? or should we rather just generate it
ourselves?  What do you/others think?

I had followed ratpoison's example (also using gentoo.org), but it does
feel dirty. I'm fine with generating it or having it stored in guix's repo,
but couldn't find an example of any other package doing the same.

+    (propagated-inputs
+     `(("ghc-mtl" ,ghc-mtl)
+       ("ghc-utf8-string" ,ghc-utf8-string)
+       ("ghc-extensible-exceptions" ,ghc-extensible-exceptions)
+       ("ghc-x11" ,ghc-x11)))

Do these inputs need to be propagated?  I can start up an xmonad
session without propagating these inputs.  Do they need to be available
for xmonad's 'mod-q' (i.e. restarting xmonad/loading a new config)?

I think so, yes. For one, since xmonad is an executable and a library, if
we don't propagate, "ghc-pkg list" will report it as broken. Manually
calling "ghc --make" on xmonad.hs (or other modules using XMonad) will
fail, and I'm assuming mod-q will also (but I confess I haven't tested:
I felt avoiding a broken package in ghc's package database was enough of
a reason for propagating the dependencies).

Siniša




reply via email to

[Prev in Thread] Current Thread [Next in Thread]