From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: helix-bin-22.03
Date: Wed, 30 Mar 2022 12:21:53 +0200 [thread overview]
Message-ID: <20220330102153.H9Kd3BgPrWpxBiKRQvToW-Wd_QfvlXsDRqq1CF7Yh8o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36414@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
New comment by tranzystorek-io on void-packages repository
https://github.com/void-linux/void-packages/pull/36414#issuecomment-1082893327
Comment:
To clarify what I meant:
1. Switch from `helix-bin` to just `helix`
2. Use `build_style=cargo`
3. Switch the distfile to the `22.03.tar.gz` source package (instead of the prebuilt binary)
4. Keep the Rust patch to fix the source code
5. Allow targets other than `x86_64`, I just built it this way for i686 so it should be fine
6. In `post_install`, move the built binary to `/usr/lib/helix/`
7. Remove the `runtime/grammars/.gitkeep` file
@paper42 Is automated fetching external files via git acceptable for source packages?
next prev parent reply other threads:[~2022-03-30 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 9:23 [PR PATCH] " shizonic
2022-03-30 9:30 ` tranzystorek-io
2022-03-30 9:45 ` [PR PATCH] [Updated] " shizonic
2022-03-30 10:10 ` tranzystorek-io
2022-03-30 10:21 ` tranzystorek-io [this message]
2022-03-30 12:06 ` leahneukirchen
2022-03-30 14:33 ` shizonic
2022-03-30 14:33 ` [PR PATCH] [Closed]: " shizonic
2022-03-30 14:35 ` tranzystorek-io
2022-03-30 14:38 ` shizonic
2022-03-30 14:39 ` shizonic
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=20220330102153.H9Kd3BgPrWpxBiKRQvToW-Wd_QfvlXsDRqq1CF7Yh8o@z \
--to=tranzystorek-io@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).