From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Some Rust packages build a lot of stuff during do_install
Date: Wed, 03 Mar 2021 16:12:39 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29207@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2775 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/29207
Description:
At least `rust-analyzer` and `angle-grinder`. Example below
```
=> rust-analyzer-2021.03.01_2: running do_install ...
Installing rust-analyzer v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/rust-analyzer)
Updating crates.io index
warning: package `pin-project-lite v0.2.4` in Cargo.lock is yanked in registry `crates.io`, consider running without --locked
Compiling once_cell v1.7.0
warning: Could not find `.git/HEAD` from manifest dir!
Compiling countme v2.0.4
Compiling thread_local v1.1.3
Compiling profile v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/profile)
Compiling rowan v0.12.6
Compiling tracing-subscriber v0.2.16
Compiling test_utils v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/test_utils)
Compiling syntax v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/syntax)
Compiling tracing-tree v0.1.8
Compiling chalk-solve v0.58.0
Compiling base_db v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/base_db)
Compiling mbe v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/mbe)
Compiling proc_macro_api v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/proc_macro_api)
Compiling hir_expand v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/hir_expand)
Compiling project_model v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/project_model)
Compiling proc_macro_srv v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/proc_macro_srv)
Compiling chalk-recursive v0.58.0
Compiling hir_def v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/hir_def)
Compiling hir_ty v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/hir_ty)
Compiling hir v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/hir)
Compiling ide_db v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/ide_db)
Compiling ide_assists v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/ide_assists)
Compiling ide_ssr v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/ide_ssr)
Compiling ide_completion v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/ide_completion)
Compiling ide v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/ide)
Compiling rust-analyzer v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/rust-analyzer)
Finished release [optimized] target(s) in 4m 07s
Installing /destdir//rust-analyzer-2021.03.01/usr/bin/rust-analyzer
Installed package `rust-analyzer v0.0.0 (/builddir/rust-analyzer-2021-03-01/crates/rust-analyzer)` (executable `rust-analyzer`)
warning: be sure to add `/destdir//rust-analyzer-2021.03.01/usr/bin` to your PATH to be able to run the installed binaries
=> rust-analyzer-2021.03.01_2: running post_install ...
```
next reply other threads:[~2021-03-03 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:12 ericonr [this message]
2021-03-03 16:09 ` leahneukirchen
2021-03-15 23:28 ` gbrlsnchs
2021-03-15 23:49 ` gbrlsnchs
2022-05-06 2:08 ` github-actions
2022-05-08 1:37 ` 0x5c
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29207@inbox.vuxu.org \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).