From: Maxime Devos <maximedevos@telenet.be>
To: Nicholas von Klitzing <nicholas@nvk.pm>,
"52107@debbugs.gnu.org" <52107@debbugs.gnu.org>
Subject: bug#52107: An Idea
Date: Fri, 26 Nov 2021 14:21:34 +0000 [thread overview]
Message-ID: <7e36114357dd0ccd37490ed3b422364c709d60a3.camel@telenet.be> (raw)
In-Reply-To: <bAnL3dryeI2AAu7UgvC9z1EUfAXIclISdBbC8IWjGUcFHmEm_-xBlkSsb7QkTJIXKaq_qsofCOV71qbWS6CEBrPrVq-7jP3QRyfZTlmTatg=@nvk.pm>
Nicholas von Klitzing schreef op vr 26-11-2021 om 09:42 [+0000]:
> Just to get the ball rolling, here is a possible idea.
>
> It might makes sense to add an additional output to the rust package
> `src` and then require this by the rust-analyzer package as
> `rust:src`.
I'd use a native-search-path instead of a wrapper setting the
environment variable, such that rust-analyzer can be used with any
version of rust and the user can override the source code used.
> In the rust-analyzer package we could then copy a thing from
> `icedove-wayland`:
> [
> ...] (call-with-output-file exe
> (lambda (port)
> (format port "#!~a
> ;; This style of overriding environment variables could be used for
> ;; RUST_SRC_PATH, although I am not sure if this is the idiomatic
> ;; way to do it.
> MOZ_ENABLE_WAYLAND=1 exec ~a $@"
'wrap-program' could be used here, instead of manually making shell
scripts.
Greetings,
Maxime
next prev parent reply other threads:[~2021-11-26 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 14:53 bug#52107: rust-analyzer shipped broken without rust-src Nicholas von Klitzing
2021-11-26 9:42 ` bug#52107: An Idea Nicholas von Klitzing
2021-11-26 14:21 ` Maxime Devos [this message]
2021-11-26 17:40 ` Nicholas von Klitzing
2021-11-26 18:07 ` Maxime Devos
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=7e36114357dd0ccd37490ed3b422364c709d60a3.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52107@debbugs.gnu.org \
--cc=nicholas@nvk.pm \
/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.