From: jnbr <jnbr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [WIP] fd: add completions
Date: Sat, 28 Mar 2020 23:01:22 +0100 [thread overview]
Message-ID: <20200328220122.6hZtzZYPynlBHsMFDAwzsxm8y583CEAHbVZKVRJkwsc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19489@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
There's a closed pull request on the void-packages repository
[WIP] fd: add completions
https://github.com/void-linux/void-packages/pull/19489
Description:
`fd` generates completion files for most shells during compilation, but the installation step doesn't add them to destdir.
~I may need some help with this, as the current template does install them (they show up in `masterdir/destdir/fd-7.4.0/` at the correct locations after `xbps-src install fd`), but they are still missing from the package after `xbps-src pkg`. I don't understand why.~ It was a caching issue...
As for using `vcopy` instead of `vinstall`, the path where the completion files are generated contains a hash. Maybe someone versed in rust's build system knows a better way than using a glob pattern.
I also noticed, that there is now a `/usr/.crates2.json` in the package, looking into it.
prev parent reply other threads:[~2020-03-28 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19489@inbox.vuxu.org>
2020-02-25 17:55 ` travankor
2020-02-26 17:11 ` crater2150
2020-02-27 17:33 ` crater2150
2020-03-28 22:01 ` jnbr [this message]
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=20200328220122.6hZtzZYPynlBHsMFDAwzsxm8y583CEAHbVZKVRJkwsc@z \
--to=jnbr@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).