From: egorenar <egorenar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] next: rename to nyxt
Date: Wed, 05 Aug 2020 21:03:42 +0200 [thread overview]
Message-ID: <20200805190342.pRAqCCxxk3t-o-2-zenPq2rjyjHiY0DUIn_6iDdJ_7I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24083@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
There is an updated pull request by egorenar against master on the void-packages repository
https://github.com/egorenar/void-packages nyxt
https://github.com/void-linux/void-packages/pull/24083
next: rename to nyxt
A patch file from https://github.com/void-linux/void-packages/pull/24083.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nyxt-24083.patch --]
[-- Type: text/x-diff, Size: 1432 bytes --]
From 2c4302bcbad9959c3ce9f1bad142e4de9b1ec5ca Mon Sep 17 00:00:00 2001
From: Alexander Egorenkov <egorenar-dev@posteo.net>
Date: Wed, 5 Aug 2020 20:54:29 +0200
Subject: [PATCH] next: rename to nyxt
---
srcpkgs/{next => nyxt}/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
rename srcpkgs/{next => nyxt}/template (68%)
diff --git a/srcpkgs/next/template b/srcpkgs/nyxt/template
similarity index 68%
rename from srcpkgs/next/template
rename to srcpkgs/nyxt/template
index cf803dd16ab..11183ab71e3 100644
--- a/srcpkgs/next/template
+++ b/srcpkgs/nyxt/template
@@ -1,5 +1,5 @@
-# Template file for 'next'
-pkgname=next
+# Template file for 'nyxt'
+pkgname=nyxt
version=1.5.0
revision=1
build_style=gnu-makefile
@@ -9,9 +9,9 @@ depends="sqlite xclip libfixposix-devel libressl-devel"
short_desc="Keyboard-oriented, extensible web-browser"
maintainer="0x0f0f0f <sudo-woodo3@protonmail.com>"
license="BSD-3-Clause"
-homepage="https://next.atlas.engineer/"
-distfiles="https://github.com/atlas-engineer/next/archive/${version}.tar.gz"
-checksum=b8688d056d40778fa6dd8ccd3ba7b5a00f16ea1e81ea8293ebe58e28f63c7e22
+homepage="https://nyxt.atlas.engineer/"
+distfiles="https://github.com/atlas-engineer/nyxt/archive/${version}.tar.gz"
+checksum=bfd1e2e6f43385b8dc07d4860da6ef99d9e94aba4c688eddd05930c5a2e36637
nostrip=yes
nopie=yes
nocross="https://travis-ci.org/void-linux/void-packages/builds/590346382"
next prev parent reply other threads:[~2020-08-05 19:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 19:02 [PR PATCH] " egorenar
2020-08-05 19:03 ` egorenar [this message]
2020-08-05 19:12 ` ericonr
2020-08-05 19:22 ` egorenar
2020-08-06 0:51 ` fosslinux
2020-09-08 12:42 ` sgn
2020-09-08 17:58 ` egorenar
2020-09-08 18:05 ` [PR PATCH] [Updated] " egorenar
2020-09-08 18:05 ` [PR PATCH] [Closed]: " egorenar
2020-09-08 18:09 [PR PATCH] " egorenar
2020-09-08 18:52 ` [PR PATCH] [Updated] " egorenar
2020-09-09 5:07 ` egorenar
2020-09-09 7:19 ` egorenar
2020-09-09 7:34 ` egorenar
2021-06-05 11:18 ` egorenar
2021-06-05 11:19 ` egorenar
2021-06-05 11:27 ` egorenar
2021-06-05 11:48 ` egorenar
2021-06-05 13:42 ` egorenar
2021-06-05 13:48 ` egorenar
2021-06-05 13:49 ` egorenar
2021-06-05 16:11 ` egorenar
2021-06-05 16:12 ` egorenar
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=20200805190342.pRAqCCxxk3t-o-2-zenPq2rjyjHiY0DUIn_6iDdJ_7I@z \
--to=egorenar@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).