From: Martin Becze <mjbecze@riseup.net>
To: guix-devel@gnu.org
Subject: Re: (not) testing Rust packages?!
Date: Sat, 25 Jan 2020 09:31:22 -0500 [thread overview]
Message-ID: <e6864022-0e19-61b2-6be2-7d3f2afe1461@riseup.net> (raw)
In-Reply-To: <6408622e-feca-c2c3-6bc3-48533336b125@crazy-compilers.com>
Part of the reason is that bringing tests for a given library can bring
in a massive amount of dependencies. So testing only the top level
package seemed like the way to go. Maybe we could add testing when
encountering problematic rust packages that break often?
On 1/25/20 8:38 AM, Hartmut Goebel wrote:
> Hi,
>
> I discovered that most packages in crates-io.scm are not build. I
> understand that this is done since they do not produce any useful output.
>
> But as an side-effect, the packages are not tested either - which might
> leave issues undiscovered.
>
> Is this intended?
>
> My experience when packaging KDE libraries showed that is does make
> sense to actually test the libraries to detect issues early. And there
> are quite some possible issue in libraries, e.g. ladoing dynamic libs
> from /usr/lib, searching executables in PATH or even worth in a
> hard-coded path.
>
next prev parent reply other threads:[~2020-01-25 14:31 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 [this message]
2020-01-25 16:46 ` John Soo
2020-01-25 17:45 ` Martin Becze
2020-01-25 22:56 ` Andreas Rottmann
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=e6864022-0e19-61b2-6be2-7d3f2afe1461@riseup.net \
--to=mjbecze@riseup.net \
--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).