From: "Paul A. Patience" <paul@apatience.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 55049@debbugs.gnu.org
Subject: [bug#55049] [PATCH 0/3] gnu: Add cl-boost-{parse,re,lexer}.
Date: Sun, 24 Apr 2022 03:29:58 +0000 [thread overview]
Message-ID: <87r15nqhu7.fsf@apatience.com> (raw)
In-Reply-To: <875yn0gpyd.fsf@kitej>
On 2022-04-23 04:23:36-04:00, Guillaume Le Vaillant wrote:
> I think you could replace the definitions of sbcl-parse, cl-parse and
> ecl-parse by:
>
> (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))
>
> and likewise for {sbcl,cl,ecl}-re. Then after some time has passed we'll
> remove the deprecated packages.
The problem is that cl-boost-parse's (CL) package name is BOOST-PARSE,
but cl-parse's package name is PARSE, so in fact they are not
transparently interchangeable.
Could we wrap the existing definitions of sbcl-parse, etc., with
deprecated-package?
Best regards,
Paul
next prev parent reply other threads:[~2022-04-24 3:31 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 ` [bug#55049] [PATCH 0/3] gnu: Add cl-boost-{parse,re,lexer} Guillaume Le Vaillant
2022-04-24 3:29 ` Paul A. Patience [this message]
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=87r15nqhu7.fsf@apatience.com \
--to=paul@apatience.com \
--cc=55049@debbugs.gnu.org \
--cc=glv@posteo.net \
/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.