[bug#52784] [PATCH 4/5 v2] Add xmonad-next and ghc-xmonad-contrib-next.

[John Kehayias via Guix-patches via <guix-patches@gnu.org>]

Hi Lars,

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Saturday, January 15th, 2022 at 5:38 AM, Lars-Dominik Braun wrote:

> Hi,
>
> > Here is version two of the patch (number 4/5) this time adding the updated xmonad and xmonad-contrib versions as new variables. I kept in the previous commit message of the changes relative to the current version (0.16), but wasn't sure if that was appropriate. The xmonad compile patch was added as a new patch and added to local.mk.
>
> It would be nice if we could use inheritance to avoid duplicated
> metadata. I implemented that on top of your changes in the attached patch,
> so when the time comes we can just delete xmonad and rename xmonad-next
> to xmonad. What do you think?
>

Yes, that makes more sense, let's go with that.

> > I don't use xmobar and wasn't sure about that, doesn't seem to have explicit dependencies on xmonad or xmonad-contrib. So I've left it as is, though I'm guessing would need to be rebased due to the line changes?
>
> I tested it and the new version works fine for me.
>

Ah, good to know. (I've been using polybar but have a huge stack of packages to add taffybar. I've been putting off submitting it because it is a lot of packages that I need to figure where each goes, but I'll get to it. If you were interested in trying out taffybar, let me know and I can make the WIP patches available for testing.)

Thanks for your work on this, I'll have to try moving my xmonad cabal setup to just Guix now.

John