Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: rust-analyzer-2020.07.13
Date: Sun, 09 Aug 2020 21:44:35 +0200	[thread overview]
Message-ID: <20200809194435.-is7pPjfxGLILrf3wC_T__rlRBEOI8udHysoQfWIEAU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23623@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/23623#issuecomment-671093133

Comment:
Does it make sense to have this as a system package? It goes hand in hand with rust development, for which someone would likely be using `rustup`. And it gets releases like crazy: https://github.com/rust-analyzer/rust-analyzer/releases

This installation step seems to indicate it depends on `rustup`, unless it can download sources without rustup: https://rust-analyzer.github.io/manual.html#installation ?

  parent reply	other threads:[~2020-08-09 19:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 18:54 [PR PATCH] " gbrlsnchs
2020-07-17 21:07 ` [PR PATCH] [Updated] " gbrlsnchs
2020-08-09  9:37 ` [PR REVIEW] " jnbr
2020-08-09  9:40 ` jnbr
2020-08-09 19:44 ` ericonr [this message]
2020-08-11  2:18 ` gbrlsnchs
2020-08-11  2:23 ` gbrlsnchs
2020-08-11  2:37 ` ericonr
2020-09-15 18:56 ` [PR PATCH] [Updated] " gbrlsnchs
2020-09-15 18:58 ` New package: rust-analyzer-2020.09.14 gbrlsnchs
2020-09-15 19:05 ` [PR REVIEW] " gbrlsnchs
2020-09-21 14:58 ` [PR PATCH] [Closed]: " gbrlsnchs
2020-09-21 23:23 ` gbrlsnchs
2020-09-21 23:35 ` [PR PATCH] [Merged]: " jnbr
2020-09-21 23:36 ` jnbr
2020-09-22  2:08 ` gbrlsnchs

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=20200809194435.-is7pPjfxGLILrf3wC_T__rlRBEOI8udHysoQfWIEAU@z \
    --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).