From: Kho-Dialga <Kho-Dialga@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: proton-caller-2.3.0
Date: Thu, 08 Jul 2021 16:22:38 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31857@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
There is a new pull request by Kho-Dialga against master on the void-packages repository
https://github.com/Kho-Dialga/void-packages master
https://github.com/void-linux/void-packages/pull/31857
New package: proton-caller-2.3.0
<!-- Mark items with [x] where applicable -->
#### General
- [x] 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.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] i686
A patch file from https://github.com/void-linux/void-packages/pull/31857.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-31857.patch --]
[-- Type: text/x-diff, Size: 1482 bytes --]
From ce6c31a4671525a3c556824c355553ee7e412489 Mon Sep 17 00:00:00 2001
From: Kho-Dialga <ivandashenyou@gmail.com>
Date: Thu, 8 Jul 2021 08:14:15 -0600
Subject: [PATCH] New package: proton-caller-2.3.0
---
srcpkgs/proton-caller/INSTALL.msg | 2 ++
srcpkgs/proton-caller/template | 16 ++++++++++++++++
2 files changed, 18 insertions(+)
create mode 100644 srcpkgs/proton-caller/INSTALL.msg
create mode 100644 srcpkgs/proton-caller/template
diff --git a/srcpkgs/proton-caller/INSTALL.msg b/srcpkgs/proton-caller/INSTALL.msg
new file mode 100644
index 000000000000..99718b588996
--- /dev/null
+++ b/srcpkgs/proton-caller/INSTALL.msg
@@ -0,0 +1,2 @@
+You need to have at least one version of Proton on your Steam folder
+and you need to have python installed as proton requires it.
diff --git a/srcpkgs/proton-caller/template b/srcpkgs/proton-caller/template
new file mode 100644
index 000000000000..1e6f92c75e86
--- /dev/null
+++ b/srcpkgs/proton-caller/template
@@ -0,0 +1,16 @@
+# Template file for 'proton-caller'
+pkgname=proton-caller
+version=2.3.0
+revision=1
+archs="x86_64 i686"
+build_style=cargo
+short_desc="Run any Windows program through Proton"
+maintainer="Iván Brito <ivandashenyou@gmail.com>"
+license="MIT"
+homepage="https://github.com/caverym/proton-caller/"
+distfiles="https://github.com/caverym/${pkgname}/archive/${version}.tar.gz"
+checksum="73908fc8fd3e4ed8cf532be5569b36f244f4b2ddd905748a2b844f49f94ab638"
+
+post_install() {
+ vlicense LICENSE
+}
next reply other threads:[~2021-07-08 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 14:22 Kho-Dialga [this message]
2021-09-21 3:37 ` [PR PATCH] [Updated] " Kho-Dialga
2021-09-21 3:39 ` Kho-Dialga
2021-09-21 3:44 ` [PR PATCH] [Updated] New package: proton-caller-2.3.2 Kho-Dialga
2021-09-21 12:25 ` Kho-Dialga
2022-05-24 2:13 ` github-actions
2022-06-08 2:11 ` [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-31857@inbox.vuxu.org \
--to=kho-dialga@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).