all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: 52181@debbugs.gnu.org
Cc: Z572 <873216071@qq.com>
Subject: bug#52181: [core-update-frozen] many rust package can't build because them source file-name use ".crate" suffix.
Date: Tue, 30 Nov 2021 15:45:00 +0200	[thread overview]
Message-ID: <YaYq3CaHb0rSE6Fb@3900XT> (raw)
In-Reply-To: <87o863owrp.fsf@qq.com>

[-- Attachment #1: Type: text/plain, Size: 766 bytes --]

On Mon, Nov 29, 2021 at 10:31:48PM +0800, Z572 via Bug reports for GNU Guix wrote:
> 
> hello,
> 
> many rust package can't build in core-update-frozen because them
> source file-name use ".crate" suffix.
> 
...
> 
> I think have 2 option:
> 
>  1. change suffix from ".crate" to ".tar.gz".
>  2. maybe let "tarball?" check file like command-line program "file", no
>  just check filename suffix.
> 

As (probably) the person who made it like that in the first place, I
like the idea of changing the suffix from '.crate'  to '.tar.gz'

-- 
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 --]

  parent reply	other threads:[~2021-11-30 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 14:31 bug#52181: [core-update-frozen] many rust package can't build because them source file-name use ".crate" suffix Z572 via Bug reports for GNU Guix
2021-11-29 14:31 ` Z572 via Bug reports for GNU Guix
2021-11-29 19:16 ` Maxime Devos
2021-11-29 19:34   ` Maxime Devos
2021-11-30 13:45 ` Efraim Flashner [this message]
2021-12-01 13:15   ` Z572 via Bug reports for GNU Guix
2021-12-01 13:15     ` Z572 via Bug reports for GNU Guix
2021-12-02  8:36     ` 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=YaYq3CaHb0rSE6Fb@3900XT \
    --to=efraim@flashner.co.il \
    --cc=52181@debbugs.gnu.org \
    --cc=873216071@qq.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 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.