From: BryceVandegrift <BryceVandegrift@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: minipro-0.6
Date: Fri, 14 Apr 2023 20:17:49 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43443@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
There is a new pull request by BryceVandegrift against master on the void-packages repository
https://github.com/BryceVandegrift/void-packages minipro
https://github.com/void-linux/void-packages/pull/43443
New package: minipro-0.6
#### Testing the changes
- I tested the changes in this PR: **YES**
#### 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-glibc)
- I built this PR locally for these architectures (if supported, mark crossbuilds):
- x86_64-musl (crossbuild)
- i686 (crossbuild)
A patch file from https://github.com/void-linux/void-packages/pull/43443.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-minipro-43443.patch --]
[-- Type: text/x-diff, Size: 1431 bytes --]
From f196952dbfd0a244d876eb46299cb3628261bdf4 Mon Sep 17 00:00:00 2001
From: Bryce Vandegrift <bryce@brycevandegrift.xyz>
Date: Fri, 14 Apr 2023 14:11:43 -0400
Subject: [PATCH] New package: minipro-0.6
---
srcpkgs/minipro/template | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 srcpkgs/minipro/template
diff --git a/srcpkgs/minipro/template b/srcpkgs/minipro/template
new file mode 100644
index 000000000000..9dd4fef528e7
--- /dev/null
+++ b/srcpkgs/minipro/template
@@ -0,0 +1,28 @@
+# Template file for 'minipro'
+pkgname=minipro
+version=0.6
+revision=1
+archs="x86_64* i686*"
+build_style=gnu-makefile
+make_use_env=compliant
+hostmakedepends="pkg-config libusb-devel"
+makedepends="libusb-devel which"
+depends="libusb"
+short_desc="Program for controlling the MiniPRO TL866xx series of chip programmers"
+maintainer="Bryce Vandegrift <bryce@brycevandegrift.xyz>"
+license="GPL-3.0-or-later"
+homepage="https://gitlab.com/DavidGriffith/minipro"
+distfiles="${homepage}/-/archive/${version}/${pkgname}-${version}.tar.gz"
+checksum=16b4220b5fc07dddc4d1d49cc181a2c6a735c833cc27f24ab73eac2572c9304a
+
+if [ "${CROSS_BUILD}" ]; then
+ hostmakedepends+=" which"
+fi
+
+post_install() {
+ vmkdir usr/lib/udev/rules.d
+ mv udev/* $DESTDIR/usr/lib/udev/rules.d
+
+ vmkdir usr/share/bash-completion/completions
+ mv bash_completion.d/minipro $DESTDIR/usr/share/bash-completion/completions
+}
next reply other threads:[~2023-04-14 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 18:17 BryceVandegrift [this message]
2023-04-14 19:42 ` Chocimier
2023-04-14 20:57 ` [PR PATCH] [Updated] " BryceVandegrift
2023-04-14 21:00 ` BryceVandegrift
2023-06-25 17:33 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43443@inbox.vuxu.org \
--to=brycevandegrift@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).