unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Rottmann <mail@r0tty.org>
To: guix-devel@gnu.org
Subject: Re: (not) testing Rust packages?!
Date: Sat, 25 Jan 2020 23:56:44 +0100	[thread overview]
Message-ID: <87tv4jxhzn.fsf@londo.h.r0tty.org> (raw)
In-Reply-To: 6e429473-5e4e-503e-fdb8-6e2b65a819f9@riseup.net

Martin Becze <mjbecze@riseup.net> writes:

> Yeah really good point there (and good work on getting all those pkgs
> in!)
>
Being a newcomer to guix, I must say I'm really amazed about the state
of Rust packaging!

>> Furthermore since most rust libraries we have are not executables, we
>> could still skip the build and run the tests I think. Aren’t the two
>> phases completely separate for cargo?
>
> Yes, will can skip the build and just test in the (cargo-build-system)
> but `cargo test` will cause most everything to build anyways i
> believe.
>
`cargo test` will always build the crate a second time, even if `cargo
build` already ran. This is due to the config attribute `test` being set
(similar a to C preprocessor #define), and thus the actual code being
compiled may be different. In addition, `cargo test` will bring in the
`dev-dependencies`, which can indeed be _much_ more massive than the
regular `dependencies`.

  reply	other threads:[~2020-01-25 22:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 13:38 (not) testing Rust packages?! Hartmut Goebel
2020-01-25 14:31 ` Martin Becze
2020-01-25 16:46   ` John Soo
2020-01-25 17:45     ` Martin Becze
2020-01-25 22:56       ` Andreas Rottmann [this message]
2020-01-27 14:49         ` John Soo
2020-01-29 19:01           ` Andreas Rottmann
2020-01-31 18:50             ` John Soo
2020-02-03 12:22               ` Hartmut Goebel
2020-01-25 18:55     ` 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

  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=87tv4jxhzn.fsf@londo.h.r0tty.org \
    --to=mail@r0tty.org \
    --cc=guix-devel@gnu.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).