From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/{rust, rust-bin}: bump to version 1.66.0
Date: Tue, 27 Dec 2022 21:49:57 +0100 [thread overview]
Message-ID: <20221227214957.3ec9866e@windsurf> (raw)
In-Reply-To: <20221224013507.2479567-1-james.hilliard1@gmail.com>
Hello James,
On Fri, 23 Dec 2022 18:35:07 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:
> Link to Rust 1.66.0 annoucement: https://blog.rust-lang.org/2022/12/15/Rust-1.66.0.html
>
> Newest version of the source archives have been retrieved with their hash values,
> and the signature of the .asc files have been verified as follows:
> $ curl -fsSL https://static.rust-lang.org/rust-key.gpg.ascii | gpg --import
> $ gpg --verify <filename.asc> <filename>
>
> There is no typographical error in the packages according to the check-pakage utility:
> $ ./utils/check-package package/rust-bin/*
> $ ./utils/check-package package/rust/*
>
> The testsuite tool were successfully run for rust and rust-bin packages to test
> the Rust toolchain under 1.66.0:
> $ ./support/testing/run-tests -k -d dl/ -o testsuite tests.package.test_rust.TestRustBin
> $ ./support/testing/run-tests -k -d dl/ -o testsuite tests.package.test_rust.TestRust
>
> In order to verify the compatibility of packages depending on Rust 1.66.0,
> tests using `./utils/test-pkg` were run.
> You may want to execute the test-pkg command after creating a `.config` file
> enabling the corresponding BR2_PACKAGE, for example:
> Create a file `buildroot/ripgrep.config` containing "BR2_PACKAGE_RIPGREP=y"
> Then execute:
> $ ./utils/test-pkg -d test-pkg -c ripgrep.config -p ripgrep
>
> Results:
> librsvg OK
> ripgrep OK
> suricata OK
> bat OK
Hmm, you know that instead of creating one snippet for each package,
you can create a single snippet that enables all those packages? It
would actually be a useful snippet to add in the commit log as it could
be useful for future updates of the Rust compiler.
> package/rust-bin/rust-bin.hash | 252 ++++++++++++++++-----------------
> package/rust-bin/rust-bin.mk | 2 +-
> package/rust/rust.hash | 6 +-
> package/rust/rust.mk | 2 +-
> 4 files changed, 131 insertions(+), 131 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-12-27 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 1:35 [Buildroot] [PATCH 1/1] package/{rust, rust-bin}: bump to version 1.66.0 James Hilliard
2022-12-27 20:49 ` Thomas Petazzoni via buildroot [this message]
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=20221227214957.3ec9866e@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox