all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: Andy Patterson <ajpatter@uwaterloo.ca>
Cc: 31548@debbugs.gnu.org
Subject: [bug#31548] [PATCH] gnu: sbcl-stumpwm: Update to 18.05.
Date: Tue, 19 Jun 2018 00:39:26 +0300	[thread overview]
Message-ID: <87r2l3ai5t.fsf_-_@gmail.com> (raw)
In-Reply-To: <20180617175916.3df21a46@uwaterloo.ca> (Andy Patterson's message of "Sun, 17 Jun 2018 17:59:16 -0400")


[-- Attachment #1.1: Type: text/plain, Size: 795 bytes --]

Hello Andy,

Andy Patterson <ajpatter@uwaterloo.ca> writes:

[…]

>> Changing “name” field unfortunatelly breaks the build.  I didn't
>> investigate a reason yet and I don't want to push without changing
>> “name” field because users will install the “stumpwm-next” by default.
>
> I haven't looked much into your patch, but this might be because the
> asdf build system uses the package name to guess where the system will
> be defined. If the package name differs from the system name, this
> behaviour can be overridden using the #:asd-system-name argument.
>
> Hope that helps

It does, thank you.  For the record ‘#:asd-system-name "stumpwm"’.

Upstream pushed a new release.  I'll test it during current week and
push the following patch probably.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: gnu: sbcl-stumpwm: Update to 18.05. --]
[-- Type: text/x-patch, Size: 1446 bytes --]

From 1e7ee0f57d46161cb655c3adcaf0f20ef12f9bdb Mon Sep 17 00:00:00 2001
From: Oleg Pykhalov <go.wigust@gmail.com>
Date: Tue, 19 Jun 2018 00:27:30 +0300
Subject: [PATCH] gnu: sbcl-stumpwm: Update to 18.05.

* gnu/packages/lisp.scm (sbcl-stumpwm): Update to 18.05.
---
 gnu/packages/lisp.scm | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index 258e9827a..720ac070c 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -944,18 +944,19 @@ from other CLXes around the net.")
 (define-public sbcl-stumpwm
   (package
     (name "sbcl-stumpwm")
-    (version "1.0.0")
+    (version "18.05")
     (source (origin
               (method url-fetch)
               (uri (string-append
                     "https://github.com/stumpwm/stumpwm/archive/"
                     version ".tar.gz"))
               (sha256
-               (base32 "1maxp98gh64az3d9vz9br6zdd6rc9fmj2imvax4by85g6kxvdz1i"))
+               (base32 "1n2gaab3lwgf5r1hmwdcw13dkv9xdd7drn2shx28kfxvhdc9kbb9"))
               (file-name (string-append "stumpwm-" version ".tar.gz"))))
     (build-system asdf-build-system/sbcl)
     (inputs `(("cl-ppcre" ,sbcl-cl-ppcre)
-              ("clx" ,sbcl-clx)))
+              ("clx" ,sbcl-clx)
+              ("alexandria" ,sbcl-alexandria)))
     (outputs '("out" "lib"))
     (arguments
      '(#:phases
-- 
2.17.1


[-- Attachment #1.3: Type: text/plain, Size: 241 bytes --]


I don't know what to do with ‘sbcl-stumpwm-next’ package.  I think we
shouldn't push it because of our policy to stick with stable versions
for recipes.  But anybody fill free to ping me if you need next version.

Regards,
Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-06-18 21:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  8:43 [bug#31548] [PATCH] gnu: Add sbcl-stumpwm-checkout Oleg Pykhalov
2018-05-23 13:03 ` Ludovic Courtès
2018-05-25 10:46   ` Oleg Pykhalov
2018-05-25 16:08     ` Ludovic Courtès
2018-06-16 22:08       ` Ludovic Courtès
2018-06-17 15:55         ` Oleg Pykhalov
2018-06-17 21:59           ` Andy Patterson
2018-06-18 21:39             ` Oleg Pykhalov [this message]
2018-06-23 22:20               ` [bug#31548] [PATCH] gnu: sbcl-stumpwm: Update to 18.05 Oleg Pykhalov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2l3ai5t.fsf_-_@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=31548@debbugs.gnu.org \
    --cc=ajpatter@uwaterloo.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.