Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] ffcall: update to 2.4.
Date: Sun, 14 Nov 2021 09:25:38 +0100	[thread overview]
Message-ID: <20211114082538.VrmKiY__ykTqM7qUfeOz3wsiffjX_RC0QTGdCkNXYbw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32722@inbox.vuxu.org>

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

There is an updated pull request by ericonr against master on the void-packages repository

https://github.com/ailiop-git/void-packages ffcall
https://github.com/void-linux/void-packages/pull/32722

ffcall: update to 2.4.
<!-- 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
- [ ] 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/32722.patch is attached

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

From b6523d02336fc1521fbda1b599a8f08bf7e3c0b1 Mon Sep 17 00:00:00 2001
From: Anthony Iliopoulos <ailiop@altatus.com>
Date: Fri, 27 Aug 2021 13:16:37 +0000
Subject: [PATCH] ffcall: update to 2.4.

---
 srcpkgs/ffcall/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/ffcall/template b/srcpkgs/ffcall/template
index 60d5f398a6c6..95072122df57 100644
--- a/srcpkgs/ffcall/template
+++ b/srcpkgs/ffcall/template
@@ -1,6 +1,6 @@
 # Template file for 'ffcall'
 pkgname=ffcall
-version=2.2
+version=2.4
 revision=1
 wrksrc="libffcall-${version}"
 build_style=gnu-configure
@@ -9,7 +9,7 @@ maintainer="Martin Riese <grauehaare@gmx.de>"
 license="GPL-2.0-or-later"
 homepage="https://www.gnu.org/software/libffcall"
 distfiles="${GNU_SITE}/libffcall/libffcall-${version}.tar.gz"
-checksum=ebfa37f97b6c94fac24ecf3193f9fc829517cf81aee9ac2d191af993d73cb747
+checksum=8ef69921dbdc06bc5bb90513622637a7b83a71f31f5ba377be9d8fd8f57912c2
 
 # won't work with parallel_build so just turn it off (thanks to JuanRP for the Hint)
 disable_parallel_build=yes
@@ -41,6 +41,7 @@ do_install() {
 }
 
 ffcall-devel_package() {
+	depends="${sourcepkg}>=${version}_${revision}"
 	short_desc+=" - development files"
 	pkg_install() {
 		vmove usr/include

  parent reply	other threads:[~2021-11-14  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 14:20 [PR PATCH] " ailiop-git
2021-08-27 17:29 ` ericonr
2021-08-27 19:42 ` [PR PATCH] [Updated] " ailiop-git
2021-11-14  8:25 ` ericonr [this message]
2021-11-14  8:27 ` ericonr
2021-11-14 13:17 ` q66
2021-11-14 14:00 ` [PR PATCH] [Closed]: " q66

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=20211114082538.VrmKiY__ykTqM7qUfeOz3wsiffjX_RC0QTGdCkNXYbw@z \
    --to=ericonr@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).