From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: elfkickers-3.2.
Date: Mon, 01 May 2023 03:57:35 +0200 [thread overview]
Message-ID: <20230501015735.yS3NrWKYA1LUVRiVtTGe1S1aRnomI1edk14gjL-Hs94@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41960@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
There is an updated pull request by zlice against master on the void-packages repository
https://github.com/zlice/void-packages elfkickers
https://github.com/void-linux/void-packages/pull/41960
New package: elfkickers-3.2.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, **x86_64**
#### Comments
Never sure on licenses - https://github.com/BR903/ELFkickers/blob/master/COPYING
Mostly manual build steps because it's so bare, not sure if there's another or better way to go about that.
A patch file from https://github.com/void-linux/void-packages/pull/41960.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-elfkickers-41960.patch --]
[-- Type: text/x-diff, Size: 1236 bytes --]
From 2b89b7bb61357644338ce46001f42b9d03fe18ff Mon Sep 17 00:00:00 2001
From: zlice <zlice555@gmail.com>
Date: Mon, 30 Jan 2023 09:22:24 -0500
Subject: [PATCH] New package: elfkickers-3.2.
---
srcpkgs/elfkickers/template | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 srcpkgs/elfkickers/template
diff --git a/srcpkgs/elfkickers/template b/srcpkgs/elfkickers/template
new file mode 100644
index 000000000000..4e2020550eda
--- /dev/null
+++ b/srcpkgs/elfkickers/template
@@ -0,0 +1,27 @@
+# Template file for 'elfkickers'
+pkgname=elfkickers
+version=3.2
+revision=1
+archs="x86_64*"
+build_style=gnu-makefile
+short_desc="Collection of ELF utilities"
+maintainer="Zlice <zlice555@gmail.com>"
+license="GPL-2.0-only"
+homepage="https://www.muppetlabs.com/~breadbox/software/elfkickers.html"
+distfiles="http://www.muppetlabs.com/~breadbox/pub/software/ELFkickers-${version}.tar.gz"
+checksum=9b81e6c53e0c94fc198d9882eb737156f36d565152dc32118897c77b06a2687c
+
+pre_build() {
+ sed "0,/prefix.*/{s/prefix.*/prefix=\/usr/}" -i Makefile
+}
+
+do_build() {
+ make ${makejobs}
+}
+
+do_install() {
+ for b in ebfc elfls elftoc infect objres rebind sstrip ; do
+ vbin bin/$b
+ vman doc/$b.1
+ done
+}
next prev parent reply other threads:[~2023-05-01 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 14:32 [PR PATCH] " zlice
2023-01-30 14:39 ` [PR PATCH] [Updated] " zlice
2023-01-30 14:41 ` zlice
2023-05-01 1:54 ` github-actions
2023-05-01 1:57 ` zlice [this message]
2023-05-01 1:58 ` zlice
2023-06-19 20:24 ` [PR PATCH] [Updated] " zlice
2023-06-25 20:14 ` [PR PATCH] [Closed]: " Duncaen
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=20230501015735.yS3NrWKYA1LUVRiVtTGe1S1aRnomI1edk14gjL-Hs94@z \
--to=zlice@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).