Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libmpack: fix license and lint
Date: Sun, 22 Aug 2021 10:47:38 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32627@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

There is a new pull request by meator against master on the void-packages repository

https://github.com/meator/void-packages libmpack
https://github.com/void-linux/void-packages/pull/32627

libmpack: fix license and lint
<!-- Mark items with [x] where applicable -->
This PR fixes a typo in `license`, it adds the license to the package and moves `make_check_target` to make `xlint` happy.
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/32627.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libmpack-32627.patch --]
[-- Type: text/x-diff, Size: 1242 bytes --]

From a376b6b2415a4c1f3f9b24cd73cab6fc8b61633e Mon Sep 17 00:00:00 2001
From: meator <coder64@protonmail.com>
Date: Sun, 22 Aug 2021 10:40:52 +0200
Subject: [PATCH] libmpack: fix license and lint

---
 srcpkgs/libmpack/template | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/libmpack/template b/srcpkgs/libmpack/template
index 8672ebeb54db..6e749f09fd57 100644
--- a/srcpkgs/libmpack/template
+++ b/srcpkgs/libmpack/template
@@ -1,18 +1,22 @@
 # Template file for 'libmpack'
 pkgname=libmpack
 version=1.0.5
-revision=1
+revision=2
 build_style=gnu-makefile
+make_check_target=test
 make_build_args="LIBTOOL=${XBPS_CROSS_BASE}/usr/bin/libtool"
 make_install_args="LIBTOOL=${XBPS_CROSS_BASE}/usr/bin/libtool"
 makedepends="libtool"
 short_desc="Simple implementation of msgpack in C"
 maintainer="Orphaned <orphan@voidlinux.org>"
-license="MTI"
+license="MIT"
 homepage="https://github.com/libmpack/libmpack"
 distfiles="https://github.com/libmpack/libmpack/archive/${version}.tar.gz"
 checksum=4ce91395d81ccea97d3ad4cb962f8540d166e59d3e2ddce8a22979b49f108956
-make_check_target=test
+
+post_install() {
+	vlicense LICENSE-MIT
+}
 
 libmpack-devel_package() {
 	depends="libmpack-${version}_${revision}"

             reply	other threads:[~2021-08-22  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22  8:47 meator [this message]
2021-08-27 17:42 ` [PR PATCH] [Merged]: " ericonr

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-32627@inbox.vuxu.org \
    --to=meator@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).