unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 52784@debbugs.gnu.org
Subject: [bug#52784] [PATCH 0/5] Update XMonad (and add new dependencies)
Date: Tue, 28 Dec 2021 19:15:11 +0000	[thread overview]
Message-ID: <nIjrGutqpVhj6vnSpYwjr978ZOodxFw1mY7fMyGpxRo6yb7XGfu6tHPE27hqOF4AIxSDwGobd5ZpegqIVEPzlvxpOdSsIvtp-KDJeAlbpTI=@protonmail.com> (raw)
In-Reply-To: <Ycrl4T40hbpOuqc6@noor.fritz.box>

Hi Lars,

Thanks for taking a look and testing.

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

On Tuesday, December 28th, 2021 at 5:24 AM, Lars-Dominik Braun wrote:

> Hi John,
>
> thanks for your patches. I also upgraded xmonad locally (see
> attached patch), but I didn’t need the version bumps/new packages
> (i.e. xmonad’s test suite builds and runs fine). Are they really
> necessary?
>

I can confirm your patch also builds and checks fine (though didn't look at the log in much detail).

Taking a quick look at the new dependency, it is for some testing but seems optional: https://github.com/xmonad/xmonad/commit/031bbd62306e592ddd0768d4e5b1105bf5e81032 So maybe that's why it builds/checks fine. Since we can easily add the needed packages, I would err on including it, what do you think?

I removed/added dependencies based on a fresh guix import and looking at the Hackage info for xmonad. I think some of the dependencies that were removed were due to older versions (or to support older GHC?) or I guess libraries that aren't needed anymore.

> > 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.
>
> I was also hesitant to push the new version for this reason. Additionally
> xmonad is part of Stackage, which we use where possible. How about adding
> a xmonad-next package instead and make the switch when Stackage includes
> the new version?
>

We do tend to follow LTS Stackage, but I wasn't sure how something like XMonad fits since I imagine most people that use it aren't using Haskell otherwise. Also, since it has been a few years since they had a release, I thought it would be nice to have it.

Anyway, an xmonad-next could make the transition easier for anyone using the previous stable release. I've been using cabal but with an update in Guix would look to make my setup more Guix-y.

To summarize, I would opt for the changes in dependencies to follow upstream, and making a separate xmonad-next avoids further disruption anyway. Personally, I also wanted to submit those new packages as part of a whole lot of Haskell packages I will be submitting to get haskell-gi and taffybar in Guix.

Thanks,
John




  reply	other threads:[~2021-12-28 19:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24 19:22 [bug#52784] [PATCH 0/5] Update XMonad (and add new dependencies) John Kehayias via Guix-patches via
2021-12-24 19:28 ` [bug#52784] [PATCH 1/5] " 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 [this message]
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='nIjrGutqpVhj6vnSpYwjr978ZOodxFw1mY7fMyGpxRo6yb7XGfu6tHPE27hqOF4AIxSDwGobd5ZpegqIVEPzlvxpOdSsIvtp-KDJeAlbpTI=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=52784@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=lars@6xq.net \
    /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).