From: Efraim Flashner <efraim@flashner.co.il>
To: "Nguyễn Gia Phong" <mcsinyx@disroot.org>
Cc: 71914-done@debbugs.gnu.org
Subject: [bug#71914] [PATCH 00/10] gnu: Add python-nh3.
Date: Wed, 3 Jul 2024 12:24:03 +0300 [thread overview]
Message-ID: <ZoUYsxiinbKbi7yn@3900XT> (raw)
In-Reply-To: <D2FSJQF3V0EU.1C4THH5P2W62V@guix>
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
On Wed, Jul 03, 2024 at 06:20:03PM +0900, Nguyễn Gia Phong wrote:
> On 2024-07-03 at 12:07+03:00, Efraim Flashner wrote:
> > On Wed, Jul 03, 2024 at 04:54:58PM +0900, Nguyễn Gia Phong wrote:
> > > Nguyễn Gia Phong (10):
> > > gnu: rust-typed-arena-2: Update to 2.0.2.
> > > gnu: Add rust-markup5ever-0.12.
> > > gnu: Add rust-html5ever-0.27.
> > > gnu: Add rust-ammonia-4.
> > > gnu: Add rust-pyo3-build-config-0.21.
> > > gnu: Add rust-pyo3-ffi-0.21.
> > > gnu: Add rust-pyo3-macros-backend-0.21.
> > > gnu: Add rust-pyo3-macros-0.21.
> > > gnu: Add rust-pyo3-0.21.
> > > gnu: Add python-nh3.
> >
> > Since it wasn't only new packages I applied this to the rust-team
> > branch, which should be merged soon-ish.
> >
> > There were a couple of missing bits, which I found while building all
> > the packages affected:
> > rust-pyo3-macros-0.21, rust-pyo3-macros-0.20:
> > Needs python-minimal as a native-input
> > rust-pyo3-macros-backend-0.21, rust-pyo3-macros-backend-0.20:
> > Needs rust-pyo3-build-config-0.2X as a cargo-input and python-minimal as
> > a native-input
> > rust-pyo3-0.21:
> > [cargo-inputs]: Added rust-chrono-tz-0.6, rust-portable-atomic-1.
> > [cargo-development-inputs]: Added rust-chrono-tz-0.6, rust-futures-0.3.
> > Removed rust-widestring-0.5.
> >
> > I used the following command to build all the packages:
> > ./pre-inst-env guix build --no-grafts --fallback --max-jobs=3 rust-typed-arena@2 rust-markup5ever@0.12 rust-html5ever@0.27 rust-ammonia@4 rust-pyo3{,-{build-config,ffi,macros-backend,macros}}@0.{20,21} python-nh3
>
> Thank you very much! So because Rust is statically compiled,
> each package needs to be (built and) tested individually?
Yeah, its an unfortunate side effect of using the sources of the
packages instead of an output. There has been talk in the upstream rust
community about providing a stable-ish interface so that we can reuse
build artifacts from one build to another.
--
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 --]
next prev parent reply other threads:[~2024-07-03 9:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 7:54 [bug#71914] [PATCH 00/10] gnu: Add python-nh3 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 01/10] gnu: rust-typed-arena-2: Update to 2.0.2 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 02/10] gnu: Add rust-markup5ever-0.12 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 03/10] gnu: Add rust-html5ever-0.27 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 04/10] gnu: Add rust-ammonia-4 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 05/10] gnu: Add rust-pyo3-build-config-0.21 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 06/10] gnu: Add rust-pyo3-ffi-0.21 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 07/10] gnu: Add rust-pyo3-macros-backend-0.21 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 08/10] gnu: Add rust-pyo3-macros-0.21 guix-patches--- via
2024-07-03 8:11 ` guix-patches--- via
2024-07-03 9:00 ` Efraim Flashner
2024-07-03 9:12 ` guix-patches--- via
2024-07-03 9:27 ` Efraim Flashner
2024-07-03 7:58 ` [bug#71914] [PATCH 09/10] gnu: Add rust-pyo3-0.21 guix-patches--- via
2024-07-03 7:58 ` [bug#71914] [PATCH 10/10] gnu: Add python-nh3 guix-patches--- via
2024-07-03 9:07 ` bug#71914: [PATCH 00/10] " Efraim Flashner
2024-07-03 9:20 ` [bug#71914] " guix-patches--- via
2024-07-03 9:24 ` Efraim Flashner [this message]
2024-07-03 9:44 ` 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=ZoUYsxiinbKbi7yn@3900XT \
--to=efraim@flashner.co.il \
--cc=71914-done@debbugs.gnu.org \
--cc=mcsinyx@disroot.org \
/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).