Github messages for voidlinux
 help / color / mirror / Atom feed
From: ankit255 <ankit255@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package:sirikali-1.5.0
Date: Sat, 02 Jul 2022 10:47:26 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37801@inbox.vuxu.org> (raw)

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

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

https://github.com/ankit255/void-packages sirikali-branch
https://github.com/void-linux/void-packages/pull/37801

New package:sirikali-1.5.0

#### Testing the changes
- I tested the changes in this PR: **YES**


#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**


#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)


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

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

From 96302ccda15860fb940f03f9ee5f848b6a054098 Mon Sep 17 00:00:00 2001
From: Ankit Pasi <ankitpasi1@gmail.com>
Date: Sat, 2 Jul 2022 14:11:23 +0530
Subject: [PATCH] New package:sirikali-1.5.0

---
 srcpkgs/sirikali/template | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 srcpkgs/sirikali/template

diff --git a/srcpkgs/sirikali/template b/srcpkgs/sirikali/template
new file mode 100644
index 000000000000..46595ce155bd
--- /dev/null
+++ b/srcpkgs/sirikali/template
@@ -0,0 +1,24 @@
+# Template file for 'sirikali'
+pkgname=sirikali
+version=1.5.0
+revision=1
+#archs="i686 x86_64"
+wrksrc="SiriKali-${version}"
+create_wrksrc=yes
+build_style=cmake
+configure_args="-DCMAKE_INSTALL_PREFIX=/usr -DQT5=true
+ -DCMAKE_BUILD_TYPE=RELEASE"
+#make_build_args=""
+#make_install_args=""
+#conf_files=""
+#make_dirs="/var/log/dir 0755 root root"
+hostmakedepends="qt5-qmake qt5-host-tools pkg-config qt5-devel"
+makedepends="libgcrypt-devel libpwquality-devel
+ libsecret-devel $(vopt_if kde kwallet-devel)"
+short_desc="GUI for cryfs, encfs, gocryptfs, securefs encrypted folders"
+maintainer="moot <realmoot@protonmail.com>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/mhogomchungu/sirikali"
+#changelog=""
+distfiles="https://github.com/mhogomchungu/sirikali/releases/download/${version}/SiriKali-${version}.tar.xz"
+checksum=848506f6130a3e10ccc3b767c4ae7b27b1f69828ef25d42dfa8d651cd3d5520e

             reply	other threads:[~2022-07-02  8:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02  8:47 ankit255 [this message]
2022-07-02 18:36 ` [PR REVIEW] " classabbyamp
2022-07-02 18:36 ` classabbyamp
2022-07-02 18:36 ` classabbyamp
2022-07-02 18:36 ` classabbyamp
2022-07-02 18:36 ` classabbyamp
2022-07-02 18:36 ` classabbyamp
2022-07-02 18:36 ` classabbyamp
2022-07-02 18:36 ` classabbyamp
2022-07-03  2:06 ` [PR PATCH] [Updated] " ankit255
2022-10-01  2:16 ` github-actions
2022-10-15  2:16 ` [PR PATCH] [Closed]: " github-actions

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