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.