all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: "Paul A. Patience" <paul@apatience.com>
Cc: 55049@debbugs.gnu.org
Subject: [bug#55049] [PATCH 0/3] gnu: Add cl-boost-{parse,re,lexer}.
Date: Sat, 23 Apr 2022 08:23:36 +0000	[thread overview]
Message-ID: <875yn0gpyd.fsf@kitej> (raw)
In-Reply-To: <20220421014937.264841-1-paul@apatience.com>

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

"Paul A. Patience" <paul@apatience.com> skribis:

> The PARSE and RE Common Lisp libraries (by https://github.com/massung) have
> been seemingly migrated to the CL-BOOST organization
> (https://github.com/cl-boost) — some of whose packages I've added in this
> patch series —, probably to avoid potential conflicts with other CL library
> names.
> For now I've left the cl-parse and cl-re Guix packages alone, but if no one is
> using them, they could be removed.
>
> Paul A. Patience (3):
>   gnu: Add cl-boost-parse.
>   gnu: Add cl-boost-re.
>   gnu: Add cl-boost-lexer.
>
>  gnu/packages/lisp-xyz.scm | 90 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 90 insertions(+)

I think you could replace the definitions of sbcl-parse, cl-parse and
ecl-parse by:

--8<---------------cut here---------------start------------->8---
(define-public sbcl-parse
  (deprecated-package "sbcl-parse" sbcl-boost-parse))

(define-public cl-parse
  (deprecated-package "cl-parse" cl-boost-parse))

(define-public ecl-parse
  (deprecated-package "ecl-parse" ecl-boost-parse))
--8<---------------cut here---------------end--------------->8---

and likewise for {sbcl,cl,ecl}-re. Then after some time has passed we'll
remove the deprecated packages.

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

  parent reply	other threads:[~2022-04-23  8:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  1:49 [bug#55049] [PATCH 0/3] gnu: Add cl-boost-{parse,re,lexer} Paul A. Patience
2022-04-21  1:52 ` [bug#55049] [PATCH 1/3] gnu: Add cl-boost-parse Paul A. Patience
2022-04-21  1:52   ` [bug#55049] [PATCH 2/3] gnu: Add cl-boost-re Paul A. Patience
2022-04-21  1:52   ` [bug#55049] [PATCH 3/3] gnu: Add cl-boost-lexer Paul A. Patience
2022-04-23  8:23 ` Guillaume Le Vaillant [this message]
2022-04-24  3:29   ` [bug#55049] [PATCH 0/3] gnu: Add cl-boost-{parse,re,lexer} Paul A. Patience
2022-04-24 10:09     ` bug#55049: " Guillaume Le Vaillant

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=875yn0gpyd.fsf@kitej \
    --to=glv@posteo.net \
    --cc=55049@debbugs.gnu.org \
    --cc=paul@apatience.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 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.