From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] micro: fix broken resource bundling.
Date: Tue, 02 Aug 2022 09:18:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38421@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
There is a new pull request by 0x5c against master on the void-packages repository
https://github.com/0x5c/void-packages fix-micro-syntax
https://github.com/void-linux/void-packages/pull/38421
micro: fix broken resource bundling.
The v2.0.11 update changed the way resources are bundled, now requiring an
additional step to 'generate' the bundle. Since I happened to only test the
original update on files that I have custom syntax for, I only realised the
presence of the regression after the update got merged (#38402).
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/38421.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix-micro-syntax-38421.patch --]
[-- Type: text/x-diff, Size: 1265 bytes --]
From ad8bcc5c857c9245bcbd52df13017f8de612ed08 Mon Sep 17 00:00:00 2001
From: 0x5c <dev@0x5c.io>
Date: Tue, 2 Aug 2022 02:27:39 -0400
Subject: [PATCH] micro: fix broken resource bundling.
The v2.0.11 update changed the way resources are bundled, now requiring an
additional step to 'generate' the bundle. Since I happened to only test the
original update on files that I have custom syntax for, I only realised the
presence of the regression after the update got merged (#38402).
---
srcpkgs/micro/template | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/micro/template b/srcpkgs/micro/template
index 8c6032324fcf..669bc7d89232 100644
--- a/srcpkgs/micro/template
+++ b/srcpkgs/micro/template
@@ -1,7 +1,7 @@
# Template file for 'micro'
pkgname=micro
version=2.0.11
-revision=1
+revision=2
build_style=go
go_import_path="github.com/zyedidia/micro/v2"
go_package="${go_import_path}/cmd/micro"
@@ -15,6 +15,10 @@ homepage="https://micro-editor.github.io"
distfiles="https://github.com/zyedidia/micro/archive/v${version}.tar.gz"
checksum=1bb499edeaaadf1fe1791a49f96ab672c4e1add31ee125882ccd85a0fc8a4abe
+pre_build() {
+ GOARCH= go generate ./runtime
+}
+
post_install() {
vlicense LICENSE
vman assets/packaging/micro.1
next reply other threads:[~2022-08-02 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 7:18 0x5c [this message]
2022-08-02 8:07 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38421@inbox.vuxu.org \
--to=0x5c@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).