Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: bees-0.7
Date: Tue, 05 Oct 2021 23:14:33 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33356@inbox.vuxu.org> (raw)

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

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

https://github.com/jcgruenhage/void-packages bees-0.7_1
https://github.com/void-linux/void-packages/pull/33356

New package: bees-0.7
<!-- 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/33356.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bees-0.7_1-33356.patch --]
[-- Type: text/x-diff, Size: 2341 bytes --]

From ea58c3a9429d211f06291b826205d5642faa7970 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Tue, 5 Oct 2021 23:05:33 +0200
Subject: [PATCH] New package: bees-0.7

---
 srcpkgs/bees/patches/Makefile.patch | 23 +++++++++++++++++++++++
 srcpkgs/bees/template               | 13 +++++++++++++
 2 files changed, 36 insertions(+)
 create mode 100644 srcpkgs/bees/patches/Makefile.patch
 create mode 100644 srcpkgs/bees/template

diff --git a/srcpkgs/bees/patches/Makefile.patch b/srcpkgs/bees/patches/Makefile.patch
new file mode 100644
index 000000000000..18b924e6a7ae
--- /dev/null
+++ b/srcpkgs/bees/patches/Makefile.patch
@@ -0,0 +1,23 @@
+diff --git a/Makefile b/Makefile
+index 9c840c4..dbff6b3 100644
+--- a/Makefile
++++ b/Makefile
+@@ -52,7 +52,7 @@ scripts: scripts/beesd scripts/beesd@.service
+ install_tools: ## Install support tools + libs
+ install_tools: src
+ 	install -Dm755 bin/fiemap $(DESTDIR)$(PREFIX)/bin/fiemap
+-	install -Dm755 bin/fiewalk $(DESTDIR)$(PREFIX)/sbin/fiewalk
++	install -Dm755 bin/fiewalk $(DESTDIR)$(PREFIX)/bin/fiewalk
+ 
+ install_bees: ## Install bees + libs
+ install_bees: src $(RUN_INSTALL_TESTS)
+@@ -60,7 +60,7 @@ install_bees: src $(RUN_INSTALL_TESTS)
+ 
+ install_scripts: ## Install scipts
+ install_scripts: scripts
+-	install -Dm755 scripts/beesd $(DESTDIR)$(PREFIX)/sbin/beesd
++	install -Dm755 scripts/beesd $(DESTDIR)$(PREFIX)/bin/beesd
+ 	install -Dm644 scripts/beesd.conf.sample $(DESTDIR)/$(ETC_PREFIX)/bees/beesd.conf.sample
+ ifneq ($(SYSTEMD_SYSTEM_UNIT_DIR),)
+ 	install -Dm644 scripts/beesd@.service $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR)/beesd@.service
+
diff --git a/srcpkgs/bees/template b/srcpkgs/bees/template
new file mode 100644
index 000000000000..f060692c9148
--- /dev/null
+++ b/srcpkgs/bees/template
@@ -0,0 +1,13 @@
+# Template file for 'bees'
+pkgname=bees
+version=0.7
+revision=1
+build_style=gnu-makefile
+hostmakedepends="git discount"
+depends="btrfs-progs"
+short_desc="Best-Effort Extent-Same, a btrfs deduplication agent"
+maintainer="Paradigm <unixparadigm@protonmail.com>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/Zygo/bees"
+distfiles="https://github.com/Zygo/bees/archive/refs/tags/v${version}.tar.gz"
+checksum=2e67422b9f0d9ef665523b474fb27055efffceb263f8ccfdfda2a3aac9c6bdb1

             reply	other threads:[~2021-10-05 21:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 21:14 jcgruenhage [this message]
2021-10-06  2:47 ` [PR REVIEW] " Vaelatern
2021-10-06  9:51 ` jcgruenhage
2021-10-06 11:08 ` jcgruenhage
2021-10-06 13:51 ` Vaelatern
2021-10-06 14:56 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-06 18:59 ` Vaelatern
2021-10-07 12:04 ` jcgruenhage
2021-10-08  9:48 ` jcgruenhage
2021-10-08 20:19 ` Chocimier
2021-10-08 23:03 ` Vaelatern
2022-03-27 10:29 ` [PR PATCH] [Updated] " jcgruenhage
2022-03-27 10:42 ` jcgruenhage
2022-03-27 10:44 ` jcgruenhage
2022-03-27 13:13 ` jcgruenhage
2022-03-27 13:17 ` jcgruenhage
2022-03-27 14:56 ` Vaelatern
2022-03-27 14:56 ` [PR PATCH] [Merged]: " Vaelatern
2022-03-27 15:05 ` jcgruenhage
2022-03-27 15:24 ` 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33356@inbox.vuxu.org \
    --to=jcgruenhage@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).