Github messages for voidlinux
 help / color / mirror / Atom feed
From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bottom: update to 0.6.0
Date: Mon, 10 May 2021 12:13:45 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30778@inbox.vuxu.org> (raw)

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

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

https://github.com/FollieHiyuki/void-packages bottom-update
https://github.com/void-linux/void-packages/pull/30778

bottom: update to 0.6.0
<!-- 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?
- [x] 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
-->

I also pull in the completions from #29455


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

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

From 87b4d67b14f193b92c351713e0e49454774e58a1 Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Mon, 10 May 2021 13:11:55 +0300
Subject: [PATCH] bottom: update to 0.6.0

Add completions
---
 srcpkgs/bottom/template | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/bottom/template b/srcpkgs/bottom/template
index 9d5fbd8dbfd0..41ed37e22dd0 100644
--- a/srcpkgs/bottom/template
+++ b/srcpkgs/bottom/template
@@ -1,6 +1,6 @@
 # Template file for 'bottom'
 pkgname=bottom
-version=0.5.7
+version=0.6.0
 revision=1
 build_style=cargo
 short_desc="Yet another cross-platform graphical process/system monitor"
@@ -8,9 +8,17 @@ maintainer="Neel Chotai <neel@chot.ai>"
 license="MIT"
 homepage="https://github.com/ClementTsang/bottom"
 distfiles="https://github.com/ClementTsang/bottom/archive/${version}.tar.gz"
-checksum=49e01a2930d913dba2a1329389faddb4b3971a6b0c08f7482d2759475d5cc27c
+checksum=3bb446439ff6ce42db2780d03e980767cfafd69e1e6a8605235dcc550fe060a1
 
 post_install() {
 	vdoc README.md
 	vlicense LICENSE
+
+	# Completions are hidden deep the build tree
+	bash_completion=$(find ${wrksrc}/target -name btm.bash | head -n1)
+	vcompletion ${bash_completion} bash btm
+	fish_completion=$(find ${wrksrc}/target -name btm.fish | head -n1)
+	vcompletion ${fish_completion} fish btm
+	zsh_completion=$(find ${wrksrc}/target -name _btm | head -n1)
+	vcompletion ${zsh_completion} zsh btm
 }

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 10:13 FollieHiyuki [this message]
2021-05-12  7:54 ` [PR PATCH] [Updated] " FollieHiyuki
2021-05-15  0:53 ` [PR PATCH] [Closed]: " ericonr

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