From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 61008@debbugs.gnu.org
Cc: ngraves@ngraves.fr
Subject: [bug#61008] [PATCH] gnu: emacs-smartparens: Fix package cl deprecation.
Date: Sun, 22 Jan 2023 17:34:46 +0100 [thread overview]
Message-ID: <87cz76ply1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20230122162913.25140-1-ngraves@ngraves.fr> (Nicolas Graves via Guix-patches via's message of "Sun, 22 Jan 2023 17:29:13 +0100")
Hello,
Nicolas Graves via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/emacs-xyz.scm (emacs-smartparens):
> [arguments] Fix package cl deprecation.
> ---
> gnu/packages/emacs-xyz.scm | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
> index ed5c3bd71d..8bde2825f1 100644
> --- a/gnu/packages/emacs-xyz.scm
> +++ b/gnu/packages/emacs-xyz.scm
> @@ -10575,6 +10575,17 @@ (define-public emacs-smartparens
> (sha256
> (base32 "0zij2f2rjjym98w68jkp10n1ckpfprlkk217c3fg16hz5nq4vnm6"))))
> (build-system emacs-build-system)
> + (arguments
> + (list
> + #:phases
> + #~(modify-phases %standard-phases
> + (add-after 'unpack 'fix-deprecated-cl-warning
> + (lambda _
> + (substitute* "smartparens.el"
> + ((string-append
> + "\\(eval-when-compile \\(require 'cl\\)\\) "
> + " ; for `lexical-let'")
> + "")))))))
AFAIU, we're fixing a mere warning. Why do you think it is worth
a patch?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2023-01-22 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 16:29 [bug#61008] [PATCH] gnu: emacs-smartparens: Fix package cl deprecation Nicolas Graves via Guix-patches via
2023-01-22 16:34 ` Nicolas Goaziou [this message]
2023-01-22 19:19 ` Nicolas Graves via Guix-patches via
2023-01-22 22:09 ` Nicolas Goaziou
2023-01-24 13:08 ` [bug#61008] [PATCH v2] gnu: emacs-smartparens: Update to 1.11.0-0.7afd647 Nicolas Graves via Guix-patches via
2023-02-07 8:08 ` bug#61008: " Christopher Baines
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=87cz76ply1.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=61008@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/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.