Github messages for voidlinux
 help / color / mirror / Atom feed
From: k4leg <k4leg@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: exfatprogs-1.1.2 
Date: Sun, 29 Aug 2021 13:33:36 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32744@inbox.vuxu.org> (raw)

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

There is a new pull request by k4leg against master on the void-packages repository

https://github.com/k4leg/void-packages New-package-exfatprogs
https://github.com/void-linux/void-packages/pull/32744

New package: exfatprogs-1.1.2 
<!-- Mark items with [x] where applicable -->

See <https://github.com/exfatprogs/exfatprogs#readme> for more info.

#### General
- [x] 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
- [x] 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/32744.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-New-package-exfatprogs-32744.patch --]
[-- Type: text/x-diff, Size: 2088 bytes --]

From b3c8b7346700733a104bbfd111f4583e9f14bf0a Mon Sep 17 00:00:00 2001
From: k4leg <python.bogdan@gmail.com>
Date: Sun, 29 Aug 2021 14:14:31 +0300
Subject: [PATCH 1/2] New package: exfatprogs-1.1.2

---
 srcpkgs/exfatprogs/template | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 srcpkgs/exfatprogs/template

diff --git a/srcpkgs/exfatprogs/template b/srcpkgs/exfatprogs/template
new file mode 100644
index 000000000000..1d37f0bc2eb7
--- /dev/null
+++ b/srcpkgs/exfatprogs/template
@@ -0,0 +1,21 @@
+# Template file for 'exfatprogs'
+pkgname=exfatprogs
+version=1.1.2
+revision=1
+build_style=gnu-configure
+hostmakedepends="autoconf automake libtool"
+short_desc="Tools to create, check and label exFAT filesystems"
+maintainer="k4leg <python.bogdan@gmail.com>"
+license="GPL-2.0-or-later"
+homepage="https://github.com/exfatprogs/exfatprogs"
+distfiles="${homepage}/archive/${version}.tar.gz"
+checksum=23cb2b709821efe9eecf10a9594be0b26d7c01192b47339902328d817c6cb358
+conflicts="exfat-utils"
+
+pre_configure() {
+	./autogen.sh
+}
+
+post_install() {
+	vdoc NEWS
+}

From 6ed53dd7fe81d118ac4dc1c05e0598e8ca6529ba Mon Sep 17 00:00:00 2001
From: k4leg <python.bogdan@gmail.com>
Date: Sun, 29 Aug 2021 14:15:35 +0300
Subject: [PATCH 2/2] exfat-utils: add `exfatprogs` to conflicts

---
 srcpkgs/exfat-utils/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/exfat-utils/template b/srcpkgs/exfat-utils/template
index 6c62704fa511..1e89e4b66909 100644
--- a/srcpkgs/exfat-utils/template
+++ b/srcpkgs/exfat-utils/template
@@ -1,7 +1,7 @@
 # Template file for 'exfat-utils'
 pkgname=exfat-utils
 version=1.3.0
-revision=1
+revision=2
 build_style=gnu-configure
 short_desc="Utilities for exFAT file system"
 maintainer="Orphaned <orphan@voidlinux.org>"
@@ -9,3 +9,4 @@ license="GPL-2.0-or-later"
 homepage="https://github.com/relan/exfat"
 distfiles="${homepage}/releases/download/v${version}/${pkgname}-${version}.tar.gz"
 checksum=dfebd07a7b907e2d603d3a9626e6440bd43ec6c4e8c07ccfc57ce9502b724835
+conflicts="exfatprogs"

             reply	other threads:[~2021-08-29 11:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 11:33 k4leg [this message]
2021-08-29 11:40 ` [PR PATCH] [Updated] " k4leg
2021-08-29 11:50 ` [PR REVIEW] " Duncaen
2021-08-29 11:51 ` [PR PATCH] [Updated] " k4leg
2021-08-29 11:52 ` k4leg
2022-03-02 21:00 ` k4leg
2022-03-02 21:02 ` [PR PATCH] [Updated] New package: exfatprogs k4leg
2022-06-03  2:11 ` github-actions
2022-06-03 13:25 ` prez
2022-06-03 13:25 ` prez
2022-06-03 19:15 ` [PR PATCH] [Merged]: " Duncaen
2022-06-03 19:23 ` sug0

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-32744@inbox.vuxu.org \
    --to=k4leg@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).