From: Efraim Flashner <efraim@flashner.co.il>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 66576@debbugs.gnu.org, 66553-done@debbugs.gnu.org
Subject: bug#66553: bug#66576: Request for merging "rust-team" branch
Date: Wed, 18 Oct 2023 11:36:41 +0300 [thread overview]
Message-ID: <ZS-ZGbsH0gx40DBU@pbp> (raw)
In-Reply-To: <87y1g1tfxk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]
On Tue, Oct 17, 2023 at 11:41:11AM -0400, Maxim Cournoyer wrote:
> Hi Efraim,
>
> Efraim Flashner <efraim@flashner.co.il> writes:
>
> > IMO rust-team branch is ready to merge. We've updated rust to 1.70,
> > librsvg to 2.56.4 and many new and updated packages. We've added a phase
> > to the cargo-build-system to fail if it detects pre-built files and
> > we've set the cargo-build-system to skip the test phase by default,
> > allowing us to make sure that the packages have the correct inputs. With
> > these changes I've gotten 100% of the packages built using the
> > cargo-build-system to build successfully.
>
> This sounds good except I don't understand how disabling the tests by
> default help to "make sure that the packages have the correct inputs" ?
>
> You've explained the rationale here:
> <https://lists.gnu.org/archive/html/guix-devel/2023-10/msg00182.html>,
> saying we sometimes use a newer Rust than the package tests are
> expecting; how does it work in the Rust world? Don't they always build
> even older versions against the most recent compiler? What about the
> test suites then? Are these not typically run by users/distributions?
I've copied your questions to the thread above and answered them there
so we can keep the discussion in one place.
> For one thing the 'guix lint' command would need to be told that
> cargo-build-system has #:tests? set to #f by default to not warn without
> reasons that '#:tests? #t' is unnecessary.
I've reverted it for now so we can get the rust-team branch merged and
continue discussing if this is a good idea or not.
--
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:[~2023-10-18 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 12:30 [bug#66576] Request for merging "rust-team" branch Efraim Flashner
2023-10-17 15:41 ` Maxim Cournoyer
2023-10-18 8:36 ` Efraim Flashner [this message]
2023-10-18 16:57 ` Maxim Cournoyer
2023-10-17 22:56 ` bug#66553: bug#66576: " Ludovic Courtès
2023-10-18 8:36 ` Efraim Flashner
[not found] ` <handler.66576.B.169745945630145.ack@debbugs.gnu.org>
2023-10-21 17:41 ` bug#66576: Acknowledgement (Request for merging "rust-team" branch) 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=ZS-ZGbsH0gx40DBU@pbp \
--to=efraim@flashner.co.il \
--cc=66553-done@debbugs.gnu.org \
--cc=66576@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.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.