Github messages for voidlinux
 help / color / mirror / Atom feed
From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: lapce 0.2.5
Date: Fri, 30 Dec 2022 04:47:12 +0100	[thread overview]
Message-ID: <20221230034712.j3QznSFncaS1G0jt8ZPRttYxyMja3dmk97bm5nwmlxw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40970@inbox.vuxu.org>

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

There is an updated pull request by zen0bit against master on the void-packages repository

https://github.com/oSoWoSo/VUR lapce
https://github.com/void-linux/void-packages/pull/40970

New package: lapce 0.2.5
#### 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 and cross build for aarch64

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

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

From 21809d6169a5acc527d9a428882eeaef0bb272b3 Mon Sep 17 00:00:00 2001
From: zenobit <zen@osowoso.xyz>
Date: Tue, 27 Dec 2022 19:12:11 +0100
Subject: [PATCH] New package: lapce 0.2.5

---
 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..9bdf55aeb599
--- /dev/null
+++ b/srcpkgs/lapce/template
@@ -0,0 +1,19 @@
+# Template file for 'lapce'
+pkgname=lapce
+version=0.2.5
+revision=1
+build_style=cargo
+hostmakedepends="cargo pkg-config"
+makedepends="fontconfig-devel gtk+3-devel openssl-devel atk-devel gdk-pixbuf-devel"
+short_desc="Lightning-fast and Powerful Code Editor written in Rust"
+maintainer="zenobit <zen@osowoso.xyz>"
+license="Apache-2.0"
+homepage="https://lapce.dev"
+distfiles="https://github.com/lapce/lapce/archive/refs/tags/v${version}.tar.gz"
+checksum=3b8357653eda77b2c85306ba9f7202e539987ada4a7b5be2018b142bb23be7e4
+
+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
+}

  parent reply	other threads:[~2022-12-30  3:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  0:49 [PR PATCH] New package: lapce 0.2.4 zen0bit
2022-12-22 21:50 ` [PR PATCH] [Updated] " zen0bit
2022-12-22 21:51 ` zen0bit
2022-12-27 18:10 ` [PR PATCH] [Updated] New package: lapce 0.2.5 zen0bit
2022-12-27 18:12 ` zen0bit
2022-12-27 18:16 ` zen0bit
2022-12-27 19:37 ` zen0bit
2022-12-27 19:52 ` zen0bit
2022-12-27 20:26 ` zen0bit
2022-12-27 20:28 ` zen0bit
2022-12-27 21:01 ` zen0bit
2022-12-28 15:05 ` jonpikum
2022-12-28 15:35 ` [PR REVIEW] " paper42
2022-12-28 15:35 ` paper42
2022-12-28 15:35 ` paper42
2022-12-30  3:47 ` zen0bit [this message]
2022-12-31  1:48 ` [PR PATCH] [Updated] " zen0bit
2022-12-31 18:19 ` zen0bit
2022-12-31 18:20 ` zen0bit
2022-12-31 18:20 ` [PR PATCH] [Closed]: " zen0bit

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=20221230034712.j3QznSFncaS1G0jt8ZPRttYxyMja3dmk97bm5nwmlxw@z \
    --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).