From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: 52784@debbugs.gnu.org
Subject: [bug#52784] [PATCH 0/5] Update XMonad (and add new dependencies)
Date: Fri, 24 Dec 2021 19:22:35 +0000 [thread overview]
Message-ID: <Za9d3f8yx-cBVXBqMap5HWIudwcVR6SvNkO_m2pQ5pPNM9UE4C4pqLBuUJpUOG8AoCVwVztLo84Rtt-kXRU5dq8qYZ4P8g5Uj1K1_C3AwJU=@protonmail.com> (raw)
Hello,
Incoming are patches to update XMonad and ghc-xmonad-contrib to the new release, 0.17.0. This required some new Haskell packages and minor changes to xmonad. I've tested this builds but haven't tried running the newer versions (currently away from my main Guix computer). I also updated xmobar (again, untested beyond building).
Note that this new version has breaking configuration changes, detailed in their announcement: https://xmonad.org/news/2021/10/27/xmonad-0-17-0.html Is that worth a news entry for guix pull? It has been a long time since xmonad released a new version, for those that stay on the stable release.
John
next reply other threads:[~2021-12-24 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 19:22 John Kehayias via Guix-patches via [this message]
2021-12-24 19:28 ` [bug#52784] [PATCH 1/5] Update XMonad (and add new dependencies) John Kehayias via Guix-patches via
2021-12-24 19:29 ` [bug#52784] [PATCH 2/5] " John Kehayias via Guix-patches via
2021-12-24 19:29 ` [bug#52784] [PATCH 3/5] " John Kehayias via Guix-patches via
2021-12-24 19:29 ` [bug#52784] [PATCH 4/5] " John Kehayias via Guix-patches via
2021-12-24 19:30 ` [bug#52784] [PATCH 5/5] " John Kehayias via Guix-patches via
2021-12-28 10:24 ` [bug#52784] [PATCH 0/5] " Lars-Dominik Braun
2021-12-28 19:15 ` John Kehayias via Guix-patches via
2022-01-10 1:54 ` [bug#52784] [PATCH 4/5 v2] Add xmonad-next and ghc-xmonad-contrib-next John Kehayias via Guix-patches via
2022-01-15 10:38 ` Lars-Dominik Braun
2022-01-15 18:49 ` John Kehayias via Guix-patches via
2022-01-17 19:32 ` bug#52784: " Lars-Dominik Braun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='Za9d3f8yx-cBVXBqMap5HWIudwcVR6SvNkO_m2pQ5pPNM9UE4C4pqLBuUJpUOG8AoCVwVztLo84Rtt-kXRU5dq8qYZ4P8g5Uj1K1_C3AwJU=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=52784@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).