From: simvux <simvux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: lapce
Date: Wed, 14 Sep 2022 23:47:41 +0200 [thread overview]
Message-ID: <20220914214741.DkLej-zG4-vqOhW7A9rjbW3DFMykvpvhx1zHFDF_1io@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39261@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
There is an updated pull request by simvux against master on the void-packages repository
https://github.com/simvux/void-packages new-package-lapce
https://github.com/void-linux/void-packages/pull/39261
New package: lapce
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/39261.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-package-lapce-39261.patch --]
[-- Type: text/x-diff, Size: 1344 bytes --]
From 8d4645d20dd3fb3138129736a57e318a0e86565f Mon Sep 17 00:00:00 2001
From: simvux <simon.larsson-general@protonmail.com>
Date: Tue, 13 Sep 2022 18:53:17 +0200
Subject: [PATCH] New package: lapce-0.2.0
---
srcpkgs/lapce/template | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100644 srcpkgs/lapce/template
diff --git a/srcpkgs/lapce/template b/srcpkgs/lapce/template
new file mode 100644
index 000000000000..939fca023e2f
--- /dev/null
+++ b/srcpkgs/lapce/template
@@ -0,0 +1,19 @@
+# Template file for 'lapce'
+pkgname=lapce
+version=0.2.0
+revision=1
+build_style=cargo
+hostmakedepends="cargo cmake pkg-config"
+makedepends="expat fontconfig-devel freetype gtk+3-devel libxcb openssl-devel glib-devel cairo-devel atk-devel gdk-pixbuf-devel"
+short_desc="Lighting-fast and powerful code editor"
+maintainer="Simon <simon.larsson-general@protonmail.com>"
+license="Apache-2.0"
+homepage="https://lapce.dev"
+distfiles="https://github.com/${pkgname}/${pkgname}/archive/v${version}.tar.gz"
+checksum=163102244c6586530bc0f0736219d38a44797b2a6d97ad37d5f6553ffc8f1a04
+
+post_install() {
+ vinstall extra/linux/dev.lapce.lapce.desktop 0644 usr/share/applications/
+ vinstall extra/linux/dev.lapce.lapce.metainfo.xml 0644 usr/share/metainfo/
+ vinstall extra/images/logo.png 0644 usr/share/pixmaps/dev.lapce.lapce.png
+}
next prev parent reply other threads:[~2022-09-14 21:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 17:10 [PR PATCH] " simvux
2022-09-13 17:14 ` [PR REVIEW] " classabbyamp
2022-09-13 17:16 ` classabbyamp
2022-09-13 17:32 ` simvux
2022-09-13 17:43 ` simvux
2022-09-13 18:44 ` [PR PATCH] [Updated] " simvux
2022-09-14 21:47 ` simvux [this message]
2022-09-17 16:53 ` New package: lapce-0.2.0 hayley
2022-12-20 13:25 ` [PR PATCH] [Closed]: " simvux
2022-12-20 13:25 ` simvux
2022-12-29 23:12 [PR PATCH] new package: lapce atk
2022-12-30 20:56 ` [PR PATCH] [Updated] " atk
2023-01-02 7:07 ` atk
2023-01-06 10:17 ` atk
2023-01-24 8:15 ` atk
2023-04-02 18:52 ` atk
2023-04-02 18:53 ` atk
2023-05-13 17:25 ` atk
2023-06-03 21:43 ` atk
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=20220914214741.DkLej-zG4-vqOhW7A9rjbW3DFMykvpvhx1zHFDF_1io@z \
--to=simvux@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).