From: Evgenii Lepikhin via Guix-patches via <guix-patches@gnu.org>
To: 54644@debbugs.gnu.org
Subject: [bug#54644] [PATCH v2 5/6] gnu: rust-serde-regex: Add 1.1.0
Date: Sat, 2 Apr 2022 00:54:36 +0300 [thread overview]
Message-ID: <eaa58a75e61578f1163af15e99ea30b45963b776.1648850075.git.e.lepikhin@corp.mail.ru> (raw)
In-Reply-To: <510db1c9dd45cfc1f1ef7b025fd81f8d4723ca94.1648850075.git.e.lepikhin@corp.mail.ru>
* gnu/packages/crates-io.scm (rust-serde-regex-1): Add 1.1.0.
---
gnu/packages/crates-io.scm | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/gnu/packages/crates-io.scm b/gnu/packages/crates-io.scm
index 1f5db8d9bc..189a0b6bd1 100644
--- a/gnu/packages/crates-io.scm
+++ b/gnu/packages/crates-io.scm
@@ -54449,6 +54449,31 @@ (define-public rust-serde-qs-0.7
commonly used by Ruby on Rails via Rack.")
(license (list license:expat license:asl2.0))))
+(define-public rust-serde-regex-1
+ (package
+ (name "rust-serde-regex")
+ (version "1.1.0")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (crate-uri "serde_regex" version))
+ (file-name (string-append name "-" version ".tar.gz"))
+ (sha256
+ (base32 "1pxsnxb8c198szghk1hvzvhva36w2q5zs70hqkmdf5d89qd6y4x8"))))
+ (build-system cargo-build-system)
+ (arguments
+ `(#:skip-build? #true
+ #:cargo-inputs
+ (("rust-regex" ,rust-regex-1))
+ #:cargo-development-inputs
+ (("rust-serde-derive" ,rust-serde-derive-1)
+ ("rust-serde-json" ,rust-serde-json-1))))
+ (home-page "https://github.com/tailhook/serde-regex")
+ (synopsis "A serde wrapper, that can be used to serialize regular expressions as strings.")
+ (description "A serde wrapper, that can be used to serialize regular expressions as strings.
+It's often useful to read regexes from configuration file.")
+ (license (list license:expat license:asl2.0))))
+
(define-public rust-serde-repr-0.1
(package
(name "rust-serde-repr")
--
2.34.0
next prev parent reply other threads:[~2022-04-01 21:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 21:21 [bug#54644] [PATCH 1/7] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:33 ` [bug#54644] [PATCH 2/7] gnu: rust-pretty 0.11: Update to 0.11.2 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:35 ` [bug#54644] [PATCH 3/7] gnu: rust-located-yaml 0.2: Update to 0.2.1 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:35 ` [bug#54644] [PATCH 4/7] gnu: rust-minimal-lexical " Evgenii Lepikhin via Guix-patches via
2022-03-31 11:59 ` Maxime Devos
2022-03-31 12:01 ` Maxime Devos
2022-03-31 14:47 ` Efraim Flashner
2022-03-31 15:40 ` Maxime Devos
2022-03-31 22:30 ` Evgenii Lepikhin via Guix-patches via
2022-04-01 6:38 ` Maxime Devos
2022-04-01 13:51 ` Evgenii Lepikhin via Guix-patches via
2022-04-01 15:32 ` Maxime Devos
2022-03-30 21:36 ` [bug#54644] [PATCH 5/7] gnu: rust-nom 7.1: Update to 7.1.1 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:37 ` [bug#54644] [PATCH 6/7] gnu: rust-serde-regex 1: Update to 1.1.0 Evgenii Lepikhin via Guix-patches via
2022-03-31 11:56 ` Maxime Devos
2022-03-31 19:16 ` Maxime Devos
2022-03-31 11:58 ` Maxime Devos
2022-03-31 14:48 ` Efraim Flashner
2022-03-30 21:37 ` [bug#54644] [PATCH 7/7] gnu: Add copyright for myself Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 1/6] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 2/6] gnu: rust-pretty 0.11: Update to 0.11.2 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 3/6] gnu: rust-located-yaml: Add 0.2.1 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 4/6] gnu: rust-nom 7: Update to 7.1.1 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` Evgenii Lepikhin via Guix-patches via [this message]
2022-04-01 21:54 ` [bug#54644] [PATCH v2 6/6] Add copyright for myself Evgenii Lepikhin via Guix-patches via
2022-05-16 13:49 ` [bug#54644] [PATCH v2 1/6] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-05-30 8:18 ` bug#54644: " Efraim Flashner
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=eaa58a75e61578f1163af15e99ea30b45963b776.1648850075.git.e.lepikhin@corp.mail.ru \
--to=guix-patches@gnu.org \
--cc=54644@debbugs.gnu.org \
--cc=e.lepikhin@corp.mail.ru \
/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.