Github messages for voidlinux
 help / color / mirror / Atom feed
From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mdBook: add completions
Date: Sun, 25 Feb 2024 17:45:06 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48934@inbox.vuxu.org> (raw)

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

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

https://github.com/meator/void-packages mdBook-completions
https://github.com/void-linux/void-packages/pull/48934

mdBook: add completions
<!-- Uncomment relevant sections and delete options which are not applicable -->

ping maintainer: @ericonr 

#### 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**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/48934.patch is attached

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

From 174387b57ce35d599764eaa44b509d65d91fe159 Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Sun, 25 Feb 2024 17:37:17 +0100
Subject: [PATCH] mdBook: add completions

---
 srcpkgs/mdBook/template | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/mdBook/template b/srcpkgs/mdBook/template
index dbebda4f3dec58..e3caf02595d6f6 100644
--- a/srcpkgs/mdBook/template
+++ b/srcpkgs/mdBook/template
@@ -1,8 +1,9 @@
 # Template file for 'mdBook'
 pkgname=mdBook
 version=0.4.37
-revision=1
+revision=2
 build_style=cargo
+build_helper=qemu
 short_desc="Create book from markdown files. Like Gitbook but implemented in Rust"
 maintainer="Érico Nogueira <ericonr@disroot.org>"
 license="MPL-2.0"
@@ -13,4 +14,9 @@ checksum=7a360cb8702d8a35d9db9d0639a6a4650d3a9492970cf772f49c5a99d981272c
 
 post_install() {
 	vlicense LICENSE
+
+	for completion in bash fish zsh; do
+		vtargetrun $DESTDIR/usr/bin/mdbook completions $completion > mdbook.$completion
+		vcompletion mdbook.$completion $completion
+	done
 }

             reply	other threads:[~2024-02-25 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 16:45 meator [this message]
2024-02-25 20:53 ` [PR PATCH] [Merged]: " classabbyamp

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