unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 33311@debbugs.gnu.org, 33311-done@debbugs.gnu.org
Subject: [bug#33311] [PATCH] gnu: Drop non-sbcl lisp support from Stumpwm 2018.05.
Date: Wed, 05 Dec 2018 07:34:00 +0300	[thread overview]
Message-ID: <87pnugpp6v.fsf@gmail.com> (raw)
In-Reply-To: <cublg582kvc.fsf@gmx.com> (Pierre Langlois's message of "Sun, 02 Dec 2018 12:06:47 +0000")

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

Hello Pierre,

Pierre Langlois <pierre.langlois@gmx.com> 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.

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

      reply	other threads:[~2018-12-05  4:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 10:01 [bug#33311] [PATCH] gnu: Drop non-sbcl lisp support from Stumpwm 2018.05 Pierre Langlois
2018-11-25 22:05 ` Pierre Langlois
2018-11-26 13:37 ` Pierre Neidhardt
2018-11-28 16:25 ` Oleg Pykhalov
2018-11-28 17:01   ` Pierre Langlois
2018-12-02 12:06     ` Pierre Langlois
2018-12-05  4:34       ` Oleg Pykhalov [this message]

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=87pnugpp6v.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=33311-done@debbugs.gnu.org \
    --cc=33311@debbugs.gnu.org \
    --cc=pierre.langlois@gmx.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).