--- Begin Message ---
|
Subject: |
[PATCH] gnu: Drop non-sbcl lisp support from Stumpwm 2018.05. |
|
Date: |
Thu, 08 Nov 2018 10:01:59 +0000 |
|
User-agent: |
mu4e 1.1.0; emacs 26.1 |
Hello Guix!
I'm in the process of switching back to StumpWM as my main window
manager, and when taking a look at the package, I realised we still
supported non-sbcl builds while upstream dropped them after version
1.0.0 [0]. So since StumpWM now only supports sbcl, I thought we should
just rename it to "stumpwm" instead of "sbcl-stumpwm", as that's
redundant. And then we can keep the ecl-stumpwm variant, but downgraded
to 1.0.0
WDYT?
Thanks,
Pierre
[0]: http://lists.nongnu.org/archive/html/stumpwm-devel/2017-01/msg00007.html
0001-gnu-Drop-non-sbcl-lisp-support-from-Stumpwm-2018.05.patch
Description: Text Data
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: [bug#33311] [PATCH] gnu: Drop non-sbcl lisp support from Stumpwm 2018.05. |
|
Date: |
Wed, 05 Dec 2018 07:34:00 +0300 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hello Pierre,
Pierre Langlois <address@hidden> writes:
> What about the pure CL source version, should I remove that one too? I
> guess it doesn't hurt to keep it.
I'm not agree to remove it because I don't understand a build system.
The build farm succeeds to “build” it as I am. According to a build
system documentation:
Additionally, the corresponding source package should be labeled
using the same convention as python packages (see *note Python
Modules::), using the ‘cl-’ prefix.
https://www.gnu.org/software/guix/manual/en/html_node/Build-Systems.html
I think you might want to start a discussion on guix-devel.
> Here's the updated patch. I've removed ecl-stumpwm but kept the pure
> source cl-stumpwm variant.
LGTM with minor changes in commit message,
pushed as 4b193da3f959244112a85f996d630aa1ed6d0902
Thanks,
Oleg.
signature.asc
Description: PGP signature
--- End Message ---