From: Zapeth <Zapeth@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request:
Date: Tue, 02 May 2023 17:50:14 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43716@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
New issue by Zapeth on void-packages repository
https://github.com/void-linux/void-packages/issues/43716
Description:
### Package name
rust-src
### Package homepage
https://github.com/rust-lang/rust
### Description
It looks like the [rust](https://github.com/void-linux/void-packages/blob/master/srcpkgs/rust/template) package is missing the std and core source files that would normally be required for language-servers to provide analysis (ie `rust-analyzer`).
I'm not sure what configuration steps would be necessary to provide the source files as a separate package, it seems it might be possible to include them in the build with the [`extended`](https://github.com/rust-lang/rust/blob/98c33e47a495fbd7b22bce9ce32f2815991bc414/config.example.toml#L293) and [`tools`](https://github.com/rust-lang/rust/blob/98c33e47a495fbd7b22bce9ce32f2815991bc414/config.example.toml#L303-L312) settings in the package `config.toml`.
Alpine also provides it as a separate package (https://pkgs.alpinelinux.org/package/v3.17/community/x86_64/rust-src), but I don't know how much can be gleaned from that, if anything.
Sidenote: `rust-analyzer` currently doesn't work out of the box with the `rust` package due to the missing sources, setting up this package and adding it as a dependency to `rust-analyzer` should hopefully fix that
### Does the requested package meet the package requirements?
Required
### Is the requested package released?
Yes
next reply other threads:[~2023-05-02 15:50 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 15:50 Zapeth [this message]
2023-05-03 11:16 ` Package request: rust-src tranzystorek-io
2023-05-03 12:54 ` Zapeth
2023-05-03 17:51 ` classabbyamp
2023-05-04 8:11 ` nekopsykose
2023-05-04 19:33 ` tranzystorek-io
2023-05-04 19:45 ` classabbyamp
2023-06-06 11:15 ` tranzystorek-io
2023-06-16 21:14 ` Zapeth
2023-06-16 21:14 ` [ISSUE] [CLOSED] " Zapeth
-- strict thread matches above, loose matches on Subject: below --
2024-04-22 2:52 [ISSUE] Package request: SnowCat007
2024-04-17 16:18 zengjiapei3000
2024-03-10 11:51 anon-lestat
2024-01-19 18:47 d-Tal
2024-01-16 23:00 kutu-dev
2024-01-01 12:44 random-rando
2023-12-30 23:47 CwalkPinoy
2023-12-29 16:36 michalszmidt
2023-11-01 0:34 endigma
2023-10-07 8:31 kobzar
2023-09-22 18:15 illusioon
2023-09-12 17:27 illusioon
2023-09-07 14:00 akawama
2023-08-31 15:15 bormosLP
2023-08-28 11:39 xmszkn
2023-08-07 17:01 itsdeadguy
2023-08-04 19:27 justinesmithies
2023-08-04 19:25 justinesmithies
2023-08-04 19:24 justinesmithies
2023-07-14 19:22 DeityLamb
2023-06-30 6:37 HoboDev
2023-06-25 15:42 Calandracas606
2023-06-18 23:32 ahall
2023-06-13 17:40 cendillion
2023-05-07 9:16 TeddyDD
2023-04-26 4:42 hervyqa
2023-02-20 11:26 usernamer-git
2023-01-31 17:51 timsofteng
2023-01-22 22:16 tranzystorek-io
2023-01-18 6:21 HoboDev
2023-01-13 15:24 DirtyVoid
2023-01-10 1:55 Doge222222
2022-12-31 1:16 uti5
2022-12-21 18:35 n3v3rde4d
2022-12-02 14:27 Vlasov1996
2022-12-02 14:24 Vlasov1996
2022-11-17 15:16 TeddyDD
2022-11-06 12:18 paoloschi
2022-09-30 15:48 illusioon
2022-09-18 16:37 usernamer-git
2022-09-12 0:23 1204-Wu-Brian
2022-09-10 10:53 Cloufish
2022-09-07 10:16 moilong
2022-08-30 12:37 mnipritom
2022-08-15 12:27 LinArcX
2022-07-20 17:46 dirkson
2022-07-11 20:19 Erennedirlo
2022-07-10 6:48 InfRandomness
2022-06-25 16:02 fluentpwn
2021-08-19 9:44 [ISSUE] [package request] eoli3n
2020-04-22 7:34 [ISSUE] Package Request: Anachron
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-43716@inbox.vuxu.org \
--to=zapeth@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).