From: bertronika <bertronika@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] uthash: update to 2.3.0.
Date: Sat, 02 Oct 2021 17:48:49 +0200 [thread overview]
Message-ID: <20211002154849.S1MM-4p3kAWnBdDSp_c8VOB_8qQiKDaQ6y350LjRVzs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33265@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]
There is an updated pull request by bertronika against master on the void-packages repository
https://github.com/bertronika/void-packages uthash
https://github.com/void-linux/void-packages/pull/33265
uthash: update to 2.3.0.
<!-- 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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.)
- [x] I built this PR locally for my native architecture, (x86_64)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
I haven't done any crossbuilds since this is a header-only library. Project's ChangeLog.txt doesn't mention any changes regarding system architectures, so I believe we should be fine.
The 2.3.0 version is used in one of programs I'm developing, and no errors regarding the library are generated.
A patch file from https://github.com/void-linux/void-packages/pull/33265.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-uthash-33265.patch --]
[-- Type: text/x-diff, Size: 1192 bytes --]
From cd71918e3a6a7e964360d600970cf631d2c969b7 Mon Sep 17 00:00:00 2001
From: bertronika <nejc@bertoncelj.eu.org>
Date: Sat, 2 Oct 2021 15:30:10 +0200
Subject: [PATCH] uthash: update to 2.3.0.
Upstream changelog has been added and short description now passes
xlint.
---
srcpkgs/uthash/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/uthash/template b/srcpkgs/uthash/template
index dd689bd7ebc0..6aa2f663db7a 100644
--- a/srcpkgs/uthash/template
+++ b/srcpkgs/uthash/template
@@ -1,13 +1,14 @@
# Template file for 'uthash'
pkgname=uthash
-version=2.1.0
+version=2.3.0
revision=1
-short_desc="A hash table for C structures"
+short_desc="Hash table for C structures"
maintainer="Diogo Leal <diogo@diogoleal.com>"
license="BSD-2-Clause"
homepage="http://troydhanson.github.com/uthash/"
+changelog="https://raw.githubusercontent.com/troydhanson/uthash/master/doc/ChangeLog.txt"
distfiles="https://github.com/troydhanson/uthash/archive/v${version}.tar.gz"
-checksum=152ccd8e64d0f495377232e3964d06c7ec8bb8c3fbd3217f8a5702614f9a669e
+checksum=e10382ab75518bad8319eb922ad04f907cb20cccb451a3aa980c9d005e661acc
do_install() {
vmkdir usr/include
next prev parent reply other threads:[~2021-10-02 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 13:50 [PR PATCH] " bertronika
2021-10-02 14:45 ` Chocimier
2021-10-02 15:48 ` bertronika [this message]
2021-10-02 15:54 ` bertronika
2021-10-25 20:32 ` Piraty
2021-10-25 20:34 ` [PR PATCH] [Closed]: " Piraty
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=20211002154849.S1MM-4p3kAWnBdDSp_c8VOB_8qQiKDaQ6y350LjRVzs@z \
--to=bertronika@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).