Github messages for voidlinux
 help / color / mirror / Atom feed
From: yoshiyoshyosh <yoshiyoshyosh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bfs: add to find alternatives group.
Date: Mon, 14 Aug 2023 20:40:14 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45607@inbox.vuxu.org> (raw)

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

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

https://github.com/yoshiyoshyosh/void-packages bfs
https://github.com/void-linux/void-packages/pull/45607

bfs: add to find alternatives group.
- I tested the changes in this PR: **YES**
- I built this PR locally for my native architecture, `x86_64`

`bfs` is 100% compatible with POSIX `find` by default (all valid POSIX `find` commands are valid and follow POSIX guidelines in `bfs`, though it does have its own extensions)

A patch file from https://github.com/void-linux/void-packages/pull/45607.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bfs-45607.patch --]
[-- Type: text/x-diff, Size: 1027 bytes --]

From f446adb45be6eb88d2030a5f1b9d6c0b0fc98b66 Mon Sep 17 00:00:00 2001
From: yosh <yosh-git@riseup.net>
Date: Mon, 14 Aug 2023 13:32:27 -0500
Subject: [PATCH] bfs: add to find alternatives group.

---
 srcpkgs/bfs/template | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/bfs/template b/srcpkgs/bfs/template
index 921cd2e3e1758..4f5ded918eb51 100644
--- a/srcpkgs/bfs/template
+++ b/srcpkgs/bfs/template
@@ -1,7 +1,7 @@
 # Template file for 'bfs'
 pkgname=bfs
 version=3.0.1
-revision=1
+revision=2
 build_style=gnu-makefile
 makedepends="acl-devel libcap-devel oniguruma-devel"
 checkdepends="acl-progs libcap-progs"
@@ -13,6 +13,11 @@ changelog="https://raw.githubusercontent.com/tavianator/bfs/main/docs/CHANGELOG.
 distfiles="https://github.com/tavianator/bfs/archive/${version}.tar.gz"
 checksum=a38bb704201ed29f4e0b989fb2ab3791ca51c3eff90acfc31fff424579bbf962
 
+alternatives="
+ find:find:/usr/bin/bfs
+ find:find.1:/usr/share/man/man1/bfs.1
+"
+
 post_install() {
 	vlicense LICENSE
 }

             reply	other threads:[~2023-08-14 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 18:40 yoshiyoshyosh [this message]
2023-09-10 21:02 ` yoshiyoshyosh
2023-09-10 21:02 ` [PR PATCH] [Closed]: " yoshiyoshyosh

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