[PR PATCH] serd: update to 0.30.10.

[PR PATCH] serd: update to 0.30.10.

[tibequadorian]

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

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

https://github.com/tibequadorian/void-packages serd
https://github.com/void-linux/void-packages/pull/29317

serd: update to 0.30.10.
enable tests

<!-- Mark items with [x] where applicable -->

#### 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/29317.patch is attached

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

From 9e087206beb11b70b311ec84ca8cb4805f3001a7 Mon Sep 17 00:00:00 2001
From: tibequadorian <tibequadorian@posteo.de>
Date: Mon, 8 Mar 2021 15:35:16 +0100
Subject: [PATCH] serd: update to 0.30.10.

enable tests
---
 srcpkgs/serd/template | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/serd/template b/srcpkgs/serd/template
index f639412f20c..b024f166830 100644
--- a/srcpkgs/serd/template
+++ b/srcpkgs/serd/template
@@ -1,6 +1,6 @@
 # Template file for 'serd'
 pkgname=serd
-version=0.30.6
+version=0.30.10
 revision=1
 build_style=waf3
 short_desc="Lightweight C library for RDF syntax"
@@ -8,7 +8,15 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="ISC"
 homepage="http://drobilla.net/software/serd/"
 distfiles="http://download.drobilla.net/${pkgname}-${version}.tar.bz2"
-checksum=f5a2c74c659d8b318059068f135a43a3771491c367b6947e053a713b23cd37ef
+checksum=affa80deec78921f86335e6fc3f18b80aefecf424f6a5755e9f2fa0eb0710edf
+
+if [ "${XBPS_CHECK_PKGS}" ]; then
+	configure_args+=" --test"
+fi
+
+do_check() {
+	./waf test
+}
 
 post_install() {
 	vlicense COPYING

Re: [PR REVIEW] serd: update to 0.30.10.

[ericonr]

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

New review comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/29317#discussion_r589544273

Comment:
Maybe we can add this to the build style? what do you think?

Re: [PR REVIEW] serd: update to 0.30.10.

[tibequadorian]

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

New review comment by tibequadorian on void-packages repository

https://github.com/void-linux/void-packages/pull/29317#discussion_r589551068

Comment:
Yes I think too! 

Re: [PR REVIEW] serd: update to 0.30.10.

[tibequadorian]

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

New review comment by tibequadorian on void-packages repository

https://github.com/void-linux/void-packages/pull/29317#discussion_r589556476

Comment:
But I don't know if I'm ready to mess around with the build styles :D

Re: [PR PATCH] [Merged]: serd: update to 0.30.10.

[ericonr]

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

There's a merged pull request on the void-packages repository

serd: update to 0.30.10.
https://github.com/void-linux/void-packages/pull/29317

Description:
enable tests

<!-- Mark items with [x] where applicable -->

#### 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
-->

Re: [PR REVIEW] serd: update to 0.30.10.

[ericonr]

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

New review comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/29317#discussion_r589704608

Comment:
I will leave this as a future improvement, we can check if other waf stuff also has tests.

Re: [PR REVIEW] serd: update to 0.30.10.

[tibequadorian]

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

New review comment by tibequadorian on void-packages repository

https://github.com/void-linux/void-packages/pull/29317#discussion_r589790263

Comment:
It looks like `waf test` is officially documented, but doesn't always exist. And I didn't find a way to check if a build script contains a test task or not, like with `make -q`