From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] octoxbps: update to 0.3.2
Date: Wed, 27 Sep 2023 04:31:18 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46283@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
There is a new pull request by zen0bit against master on the void-packages repository
https://github.com/oSoWoSo/VUR octoxbps
https://github.com/void-linux/void-packages/pull/46283
octoxbps: update to 0.3.2
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x64 glibc)
I am not sure if post install message will be shown.
Inastallation with xi don't show me it..
A patch file from https://github.com/void-linux/void-packages/pull/46283.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-octoxbps-46283.patch --]
[-- Type: text/x-diff, Size: 1874 bytes --]
From af95158ccace236027c927df3f04e5baac3fef0e Mon Sep 17 00:00:00 2001
From: zenobit <zen@osowoso.xyz>
Date: Wed, 27 Sep 2023 03:56:00 +0200
Subject: [PATCH] octoxbps: update to 0.3.2
---
srcpkgs/octoxbps/files/README.voidlinux | 1 +
srcpkgs/octoxbps/template | 12 ++++++++----
2 files changed, 9 insertions(+), 4 deletions(-)
create mode 100644 srcpkgs/octoxbps/files/README.voidlinux
diff --git a/srcpkgs/octoxbps/files/README.voidlinux b/srcpkgs/octoxbps/files/README.voidlinux
new file mode 100644
index 0000000000000..7764e3960a2c4
--- /dev/null
+++ b/srcpkgs/octoxbps/files/README.voidlinux
@@ -0,0 +1 @@
+octoxbps will need sudo or opendoas installed for elevation privileges
diff --git a/srcpkgs/octoxbps/template b/srcpkgs/octoxbps/template
index e7f7cb0e167cb..a6b55fcb84773 100644
--- a/srcpkgs/octoxbps/template
+++ b/srcpkgs/octoxbps/template
@@ -1,18 +1,18 @@
# Template file for 'octoxbps'
pkgname=octoxbps
-version=0.3.1
+version=0.3.2
revision=1
build_style=qmake
hostmakedepends="qt5-qmake pkg-config qt5-host-tools"
makedepends="qt5-declarative-devel qtermwidget-devel"
-depends="curl sudo"
+depends="curl"
short_desc="Qt-based XBPS front-end"
maintainer="beefcurtains <beefcurtains@voidlinux.org>"
license="GPL-2.0-or-later"
-homepage="https://github.com/aarnt/octoxbps"
+homepage="https://tintaescura.com/projects/octopi/"
changelog="https://raw.githubusercontent.com/aarnt/octoxbps/master/CHANGELOG"
distfiles="https://github.com/aarnt/octoxbps/archive/v${version}.tar.gz"
-checksum=0ec95b8f79a1536cb7b7d2e0ac56175972a3ca77fb0ba67a7e190f592644a088
+checksum=8fe3ec0bb5eb55f94e8db08dc570ef10f61c929dfd0c12d8415d6f8d83e1c9ed
post_configure() {
local qmake_args
@@ -44,3 +44,7 @@ do_install() {
cd $_dir && make INSTALL_ROOT=${DESTDIR} install
done
}
+
+post_install() {
+ vdoc "${FILESDIR}/README.voidlinux"
+}
next reply other threads:[~2023-09-27 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 2:31 zen0bit [this message]
2023-09-28 17:24 ` classabbyamp
2023-09-28 17:24 ` [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-46283@inbox.vuxu.org \
--to=zen0bit@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).