Received: from listserv.local (listserv [172.16.8.22])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTP id 41088781142;
	Fri, 18 Feb 2022 12:35:26 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: "S.M Mukarram Nainar" <theone@sm2n.ca>
From: alice <no-reply@dispatch.alpinelinux.org>
Cc: ~alpine/aports@lists.alpinelinux.org
In-Reply-To: 
 <164518754245.985.15206621881530857624.gitlab.31077.dfc5319443230b19df6e04b88a717295e5dadda0@listserv.local>
Subject: Re: [PATCH] testing/rust-analyzer: new aport
Date: Fri, 18 Feb 2022 12:35:26 -0000
Message-ID: 
 <164518772623.985.8385715085860625316.gitlab.31077.dfc5319443230b19df6e04b88a717295e5dadda0@listserv.local>

On Fri, 18 Feb 2022 07:25:07 -0500, S.M Mukarram Nainar wrote:
> +
> +package() {
> +	install -Dm755 "$pkgdir"/usr/bin target/release/rust-analyzer

if the cargo install ever actually did something useful like move some various extra files for you then i would get it, but 99% of the time it is identical to the cp and you have to rm -r some random folder it makes, so what exactly is the point? even in multi-bin projects you invoke `cargo install` once per individual binary, like in wezterm, so it saves absolutely nothing in 'complexity' of installing some build object

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/31077#note_216553