From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] helix: update to 22.12
Date: Wed, 07 Dec 2022 13:00:06 +0100 [thread overview]
Message-ID: <20221207120006.i9VUhO9uRHbVux8yvFzwAJaF4aFSIXkFsaQj9SPaHbQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40954@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
There is an updated pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages helix
https://github.com/void-linux/void-packages/pull/40954
helix: update to 22.12
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/40954.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-helix-40954.patch --]
[-- Type: text/x-diff, Size: 1299 bytes --]
From ef28c7efdac8ff419598a3d7e64649d380603362 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Wed, 7 Dec 2022 10:39:24 +0100
Subject: [PATCH] helix: update to 22.12
---
srcpkgs/helix/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/helix/template b/srcpkgs/helix/template
index 395e77c97b34..ac8850b87cfc 100644
--- a/srcpkgs/helix/template
+++ b/srcpkgs/helix/template
@@ -1,17 +1,16 @@
# Template file for 'helix'
pkgname=helix
-version=22.08.1
+version=22.12
revision=1
build_style=cargo
make_install_args="--path helix-term"
-hostmakedepends="git"
short_desc="Post-modern modal text editor"
maintainer="Marcin Puc <tranzystorek.io@protonmail.com>"
license="MPL-2.0"
homepage="https://helix-editor.com/"
changelog="https://raw.githubusercontent.com/helix-editor/helix/master/CHANGELOG.md"
-distfiles="https://github.com/helix-editor/helix/archive/refs/tags/${version}.tar.gz"
-checksum=c9b184d53bab51e7a9fe81dc8c191a853177abba67ea408e968937f31b50b45a
+distfiles="https://github.com/helix-editor/helix/releases/download/${version}/helix-${version}-source.tar.xz"
+checksum=295b42a369fbc6282693eb984a77fb86260f7baf3ba3a8505d62d1c619c2f3f4
# skip problematic doctests on i686
case "$XBPS_TARGET_MACHINE" in
next prev parent reply other threads:[~2022-12-07 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 9:40 [PR PATCH] " tranzystorek-io
2022-12-07 12:00 ` tranzystorek-io [this message]
2022-12-07 15:29 ` [PR PATCH] [Merged]: " leahneukirchen
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=20221207120006.i9VUhO9uRHbVux8yvFzwAJaF4aFSIXkFsaQj9SPaHbQ@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).