Github messages for voidlinux
 help / color / mirror / Atom feed
From: anubhavkini <anubhavkini@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nnn: add desktop entry
Date: Sat, 29 May 2021 12:59:00 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31204@inbox.vuxu.org> (raw)

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

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

https://github.com/anubhavkini/void-packages nnn
https://github.com/void-linux/void-packages/pull/31204

nnn: add desktop entry
<!-- 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
-->


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

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

From 693957c7dbe757bb5f00441bb560333724915db8 Mon Sep 17 00:00:00 2001
From: Anubhav Kini <anubhavkini@gmail.com>
Date: Sat, 29 May 2021 16:25:29 +0530
Subject: [PATCH] nnn: add desktop entry

---
 srcpkgs/nnn/template | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/nnn/template b/srcpkgs/nnn/template
index 467ad2ec0dea..6d84a231dc9b 100644
--- a/srcpkgs/nnn/template
+++ b/srcpkgs/nnn/template
@@ -1,7 +1,7 @@
 # Template file for 'nnn'
 pkgname=nnn
 version=4.0
-revision=1
+revision=2
 build_style=gnu-makefile
 hostmakedepends="pkg-config"
 makedepends="ncurses-devel readline-devel"
@@ -21,5 +21,7 @@ post_install() {
 	vinstall misc/auto-completion/fish/nnn.fish 644 \
 		usr/share/fish/vendor_completions.d
 
+	PREFIX="$DESTDIR/usr" make install-desktop
+
 	vlicense LICENSE
 }

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 10:59 anubhavkini [this message]
2021-05-29 11:07 ` Duncaen
2021-05-29 11:56 ` [PR PATCH] [Updated] " anubhavkini
2021-05-29 12:09 ` anubhavkini
2021-05-31 14:18 ` [PR PATCH] [Merged]: " 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-31204@inbox.vuxu.org \
    --to=anubhavkini@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).