From: Vaelatern <Vaelatern@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Hooktftp
Date: Mon, 27 Apr 2020 17:46:36 +0200 [thread overview]
Message-ID: <20200427154636.t_a_DG_034E8mm3ecCsoZRSoW5mLCp2gIlr0_0sKk4k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21194@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
There is an updated pull request by Vaelatern against master on the void-packages repository
https://github.com/Vaelatern/void-packages hooktftp
https://github.com/void-linux/void-packages/pull/21194
Hooktftp
Side-downgrade to the latest git commit. I've talked to upstream about tagging actual releases so it can be better flagged as out of date. I've also talked about their packaging, and hope to encourage the software becoming more package able.
@thypon can I take maintainership? I found myself using this recently, found bugs in the ancient version we were using.
A patch file from https://github.com/void-linux/void-packages/pull/21194.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hooktftp-21194.patch --]
[-- Type: text/x-diff, Size: 1554 bytes --]
From 561cde6f8cedf91cb1d0e9a416201e9172f2577f Mon Sep 17 00:00:00 2001
From: Toyam Cox <Vaelatern@voidlinux.org>
Date: Mon, 20 Apr 2020 19:16:52 -0400
Subject: [PATCH] hooktftp: update to 1.1.0.
And adopt, since Vaelatern uses this now.
---
srcpkgs/hooktftp/template | 26 ++++++++++----------------
1 file changed, 10 insertions(+), 16 deletions(-)
diff --git a/srcpkgs/hooktftp/template b/srcpkgs/hooktftp/template
index abee0ccefd1..e1e669154b4 100644
--- a/srcpkgs/hooktftp/template
+++ b/srcpkgs/hooktftp/template
@@ -1,24 +1,18 @@
# Template file for 'hooktftp'
pkgname=hooktftp
-version=1.0.0
-revision=8
-_gitcommit="a7258310669522806b903c9ffc98ad7c62b02d56"
-wrksrc="${pkgname}-${_gitcommit}"
-hostmakedepends="go bzr git"
+version=1.1.0
+revision=1
+build_style=go
+go_import_path="github.com/tftp-go-team/hooktftp"
+go_package="github.com/tftp-go-team/hooktftp/cmd/hooktftp"
+hostmakedepends="bzr git"
short_desc="Hook based tftp server"
-maintainer="Andrea Brancaleoni <abc@pompel.me>"
+maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
license="MIT"
homepage="https://github.com/tftp-go-team/hooktftp"
-distfiles="${homepage}/archive/${_gitcommit}.tar.gz"
-checksum=42cbe6c402aee13722cb55ac1e3a22fc6be27c6313b7c59d7a7277c0e3a6065e
-nocross=yes
-nopie=yes
+distfiles="https://github.com/tftp-go-team/hooktftp/archive/${version}.tar.gz"
+checksum=74a29947509a4a718091a5571cc2b2bdbfae807499f06beae124e78afdc56cf9
-do_build() {
- GOPATH=$PWD make build
-}
-
-do_install() {
+post_install() {
vlicense LICENSE
- vbin src/${pkgname}
}
next prev parent reply other threads:[~2020-04-27 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 23:44 [PR PATCH] Hooktftp Vaelatern
2020-04-27 15:46 ` Vaelatern [this message]
2020-04-27 15:47 ` Hooktftp Vaelatern
2020-04-27 15:54 ` [PR PATCH] [Merged]: Hooktftp Vaelatern
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=20200427154636.t_a_DG_034E8mm3ecCsoZRSoW5mLCp2gIlr0_0sKk4k@z \
--to=vaelatern@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).