unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: VesselWave <VesselWave@protonmail.com>,
	"57702@debbugs.gnu.org" <57702@debbugs.gnu.org>
Subject: [bug#57702] [PATCH 1/8] gnu: Add rust-unic-emoji-char-0.9.
Date: Sat, 10 Sep 2022 02:13:11 +0200	[thread overview]
Message-ID: <76e0002e-293a-4874-0e1e-e3cbfa455592@telenet.be> (raw)
In-Reply-To: <2FM_77W4h13TjSAPpcyy8a8xVR43mgwJ09tQ9hn6-5iFxXrD6R77GtNPyYntp4T-bx18UhiS7DCf1WdcKIWjDpH2A6wwKPd-YdQEXTU1e48=@protonmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1588 bytes --]



On 09-09-2022 20:05, VesselWave via Guix-patches via wrote:
> 
> ---
>   gnu/packages/crates-io.scm | 23 +++++++++++++++++++++++
>   1 file changed, 23 insertions(+)
> 
> diff --git a/gnu/packages/crates-io.scm b/gnu/packages/crates-io.scm
> index 02f7bc7d4d..a82515f73e 100644
> --- a/gnu/packages/crates-io.scm
> +++ b/gnu/packages/crates-io.scm
> @@ -69234,6 +69234,29 @@ (define-public rust-unic-common-0.9
>   Internationalization Crates (UNIC) project.")
>       (license (list license:expat license:asl2.0))))
> 
> +(define-public rust-unic-emoji-char-0.9
> +  (package
> +    (name "rust-unic-emoji-char")
> +    (version "0.9.0")
> +    (source (origin
> +              (method url-fetch)
> +              (uri (crate-uri "unic-emoji-char" version))
> +              (file-name (string-append name "-" version ".tar.gz"))
> +              (sha256
> +               (base32
> +                "0ka9fr7s6lv0z43r9xphg9injn35pfxf9g9q18ki0wl9d0g241qb"))))

This contains various binaries (i.e., non-source, I don't mean it in the 
executable sense), see the .rsv files in 
<https://github.com/open-i18n/rust-unic/tree/master/unic/emoji/char/tables>

> // WARNING: Auto-generated by the `unic-gen` crate.
> // WARNING: DO NOT EDIT MANUALLY!


they need to be built from source instead, presumably with this 
`unic-gen`.  To make sure the binaries aren't used, they can be removed 
in the origin, with snippet ('delete-file-recursively' can be useful). 
A post-unpack phase can be useful for regenerating these binaries.

Greetings,
Maxime.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-09-10  0:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 14:18 [bug#57702] [PATCH 0/8] Update rust-clap-3 to 3.2.17 VesselWave via Guix-patches via
2022-09-09 16:03 ` [bug#57702] [PATCH v2 1/8] gnu: Add rust-unic-emoji-char-0.9 VesselWave via Guix-patches via
2022-09-09 20:30   ` ( via Guix-patches via
2022-09-09 20:33   ` ( via Guix-patches via
2022-09-09 16:04 ` [bug#57702] [PATCH v2 2/8] gnu: rust-textwrap: Add 0.15.0 VesselWave via Guix-patches via
2022-09-09 16:05 ` [bug#57702] [PATCH v2 3/8] gnu: rust-crossbeam-utils-0.8: Add development inputs VesselWave via Guix-patches via
2022-09-09 16:06 ` [bug#57702] [PATCH v2 4/8] gnu: rust-parking-lot-core: Inrerit from latest VesselWave via Guix-patches via
2022-09-09 16:09 ` [bug#57702] [PATCH v2 5/8] gnu: rust-once-cell-1: Update to 1.13.1 VesselWave via Guix-patches via
2022-09-09 16:10 ` [bug#57702] [PATCH v2 6/8] gnu: Add rust-clap-lex-0.2 VesselWave via Guix-patches via
2022-09-09 16:11 ` [bug#57702] [PATCH v2 7/8] gnu: rust-clap-derive-3: Update to 3.2.17 VesselWave via Guix-patches via
2022-09-09 16:12 ` [bug#57702] [PATCH v2 8/8] gnu: rust-clap-3: " VesselWave via Guix-patches via
2022-09-09 17:10 ` [bug#57702] [PATCH v2 0/8] " VesselWave via Guix-patches via
2022-09-09 18:05 ` [bug#57702] [PATCH 1/8] gnu: Add rust-unic-emoji-char-0.9 VesselWave via Guix-patches via
2022-09-10  0:13   ` Maxime Devos [this message]
2022-09-10  6:13 ` [bug#57702] [PATCH 2/8] gnu: rust-textwrap: Add 0.15.0 VesselWave via Guix-patches via
2022-09-10  6:14 ` [bug#57702] [PATCH 3/8] gnu: rust-crossbeam-utils-0.8: Add development inputs VesselWave via Guix-patches via
2022-09-10  6:15 ` [bug#57702] [PATCH 4/8] gnu: rust-parking-lot-core: Inrerit from latest VesselWave via Guix-patches via
2022-09-10  6:16 ` [bug#57702] [PATCH 5/8] gnu: rust-once-cell-1: Update to 1.13.1 VesselWave via Guix-patches via
2022-09-10  6:17 ` [bug#57702] [PATCH 6/8] gnu: Add rust-clap-lex-0.2 VesselWave via Guix-patches via
2022-09-10  6:17 ` [bug#57702] [PATCH 7/8] gnu: rust-clap-derive-3: Update to 3.2.17 VesselWave via Guix-patches via
2022-09-10  6:19 ` [bug#57702] [PATCH 8/8] gnu: rust-clap-3: " VesselWave via Guix-patches via
2022-09-10  8:52 ` [bug#57702] [PATCH 1/8] gnu: Add rust-nic-emoji-char-0.9 VesselWave via Guix-patches via
2022-09-10  9:38 ` [bug#57702] [PATCH v4 " VesselWave via Guix-patches via
2022-09-11 11:37   ` Maxime Devos
2022-09-12 21:00 ` [bug#57702] [PATCH 1/8] gnu: rust-termion: Update to 1.5.6 VesselWave via Guix-patches via
2022-09-13  9:14 ` [bug#57702] [PATCH 0/8] Update rust-clap-3 to 3.2.17 VesselWave via Guix-patches via
2022-09-13  9:15 ` [bug#57702] [PATCH 1/8] gnu: rust-termion-1: Update to 1.5.6 VesselWave via Guix-patches via
2022-09-13  9:18 ` [bug#57702] [PATCH 2/8] gnu: rust-textwrap: Add 0.15.0 VesselWave via Guix-patches via
2022-09-13  9:19 ` [bug#57702] [PATCH 3/8] gnu: rust-crossbeam-utils-0.8: Add development inputs VesselWave via Guix-patches via
2022-09-13  9:19 ` [bug#57702] [PATCH 4/8] gnu: rust-parking-lot-core: Inrerit from latest VesselWave via Guix-patches via
2022-09-13  9:20 ` [bug#57702] [PATCH 5/8] gnu: rust-once-cell-1: Update to 1.13.1 VesselWave via Guix-patches via
2022-09-13  9:20 ` [bug#57702] [PATCH 6/8] gnu: Add rust-clap-lex-0.2 VesselWave via Guix-patches via
2022-09-13  9:22 ` [bug#57702] [PATCH 7/8] gnu: rust-clap-derive-3: Update to 3.2.17 VesselWave via Guix-patches via
2022-09-13  9:22 ` [bug#57702] [PATCH 8/8] gnu: rust-clap-3: " VesselWave via Guix-patches via
2022-09-20 19:31 ` [bug#57702] [PATCH 0/8] Update rust-clap-3 " John Kehayias via Guix-patches via

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=76e0002e-293a-4874-0e1e-e3cbfa455592@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=57702@debbugs.gnu.org \
    --cc=VesselWave@protonmail.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 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).