From: Efraim Flashner <efraim@flashner.co.il>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 56956-done@debbugs.gnu.org
Subject: bug#56956: rust-pico-sys bundles PicoHTTPParser.
Date: Fri, 5 Aug 2022 18:22:06 +0300 [thread overview]
Message-ID: <Yu01nonUvJlF4hMP@pbp> (raw)
In-Reply-To: <251adf58-6490-0bb2-8633-6818d2314e32@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On Wed, Aug 03, 2022 at 08:18:36PM +0200, Maxime Devos wrote:
> X-Debbugs-CC: Efraim Flashner <efraim@flashner.co.il>
>
> (^ original package author+committer)
>
> rust-pico-sys was added in commit
> <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=eda57f4834b29ef17758f7f1f62d3af899e2d669>.
>
> This package bundles PicoHTTPParser.
>
> Fortunately, it is only used by a single dependency: rust-httparser, and
> only for benchmarks (which probably aren't compiled anyway), so simply
> removing the package definition and removing it from rust-httparser'
> #:dev-dependencies should be sufficient. This appears to work in
> antioxidant.
It turns out rust-httparser-1 doesn't build on its own without
rust-pico-sys-0.0, but updating rust-httparser-1 from 1.5.1 to 1.7.1
changed the development-inputs and allowed me to remove
rust-pico-sys-0.0.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-05 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 18:18 bug#56956: rust-pico-sys bundles PicoHTTPParser Maxime Devos
2022-08-05 15:22 ` Efraim Flashner [this message]
2022-08-05 15:24 ` Maxime Devos
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=Yu01nonUvJlF4hMP@pbp \
--to=efraim@flashner.co.il \
--cc=56956-done@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).