From: Rheydskey <Rheydskey@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Updated nushell and changed the source of the compilation file
Date: Tue, 17 Nov 2020 08:53:58 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26454@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
There is a new pull request by Rheydskey against master on the void-packages repository
https://github.com/Rheydskey/void-packages master
https://github.com/void-linux/void-packages/pull/26454
Updated nushell and changed the source of the compilation file
Hi,
I have updated nushell and changed the repositories of the compilation files.
Rheydskey
A patch file from https://github.com/void-linux/void-packages/pull/26454.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-26454.patch --]
[-- Type: text/x-diff, Size: 1408 bytes --]
From 53c482ddd3c86a4b4a3086cf13a3e8513f9b7f85 Mon Sep 17 00:00:00 2001
From: Rheydskey <matgag02@gmail.com>
Date: Tue, 17 Nov 2020 08:50:31 +0100
Subject: [PATCH] Updated nushell and changed the source of the compilation
file
---
srcpkgs/nushell/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/nushell/template b/srcpkgs/nushell/template
index 843eda01b71..31efa6076cf 100644
--- a/srcpkgs/nushell/template
+++ b/srcpkgs/nushell/template
@@ -1,12 +1,12 @@
# Template file for 'nushell'
pkgname=nushell
-version=0.21.0
+version=0.22.0
revision=1
# raw-cpuid does not support other archs
# https://github.com/nushell/nushell/issues/485
# remove when the issue is fixed (should fix all archs)
archs="x86_64* i686*"
-wrksrc="nu-${version}"
+wrksrc="nushell-${version}"
build_style=cargo
hostmakedepends="pkg-config"
makedepends="libressl-devel"
@@ -15,8 +15,8 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
license="MIT"
homepage="https://www.nushell.sh/"
changelog="https://www.nushell.sh/blog/"
-distfiles="https://static.crates.io/crates/nu/nu-${version}.crate"
-checksum=44b0dc4127433373d6ce1b5ba50c56780f23b861654fce3b48d5b599758e772c
+distfiles="https://github.com/nushell/nushell/archive/${version}.tar.gz"
+checksum=a7ee864b711d43bec1d611aa11ac70ff62f254d09ee507bbbe7aa3ceaf7b4f39
post_install() {
vlicense LICENSE
next reply other threads:[~2020-11-17 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 7:53 Rheydskey [this message]
2020-11-17 12:28 ` [PR REVIEW] nushell: update to 0.22.0 " ericonr
2020-11-17 12:29 ` ericonr
2020-11-17 13:46 ` nushell: update to 0.22.0, update distfile Rheydskey
2020-11-17 13:48 ` ericonr
2020-11-17 14:07 ` [PR PATCH] [Updated] " Rheydskey
2020-11-17 21:45 ` ericonr
2020-11-17 22:05 ` ericonr
2020-12-20 1:21 ` ericonr
2020-12-31 21:33 ` ericonr
2021-01-02 13:11 ` [PR PATCH] [Updated] " Rheydskey
2021-01-02 13:12 ` [PR PATCH] [Closed]: " Rheydskey
2021-01-02 13:12 ` [PR PATCH] [Updated] " Rheydskey
2021-01-02 13:14 ` Rheydskey
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-26454@inbox.vuxu.org \
--to=rheydskey@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).