Github messages for voidlinux
 help / color / mirror / Atom feed
From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [WIP] nushell: update to 0.26.0
Date: Thu, 04 Feb 2021 09:15:12 +0100	[thread overview]
Message-ID: <20210204081512.JMR5PPPA_60S9XC22LD4YOOMDaDGUN2UfcTc4DdAdck@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28341@inbox.vuxu.org>

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

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

https://github.com/FollieHiyuki/void-packages nushell
https://github.com/void-linux/void-packages/pull/28341

[WIP] nushell: update to 0.26.0
<!-- Mark items with [x] where applicable -->

#### General
- [ ] 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] 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.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


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

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

From 058e3319a79c69bef2620fffbcfc20d3d81d3a18 Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Sat, 30 Jan 2021 21:29:13 +0300
Subject: [PATCH] nushell: update to 0.26.0

---
 srcpkgs/nushell/template | 33 +++++++++++++++++++++++----------
 1 file changed, 23 insertions(+), 10 deletions(-)

diff --git a/srcpkgs/nushell/template b/srcpkgs/nushell/template
index 843eda01b71..6daf1322252 100644
--- a/srcpkgs/nushell/template
+++ b/srcpkgs/nushell/template
@@ -1,22 +1,35 @@
 # Template file for 'nushell'
 pkgname=nushell
-version=0.21.0
+version=0.26.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}"
 build_style=cargo
-hostmakedepends="pkg-config"
-makedepends="libressl-devel"
+configure_args="--features=extra"
+hostmakedepends="pkg-config libgit2-devel"
+makedepends="libressl-devel libX11-devel libxcb-devel libgit2-devel"
 short_desc="Modern shell for the GitHub era"
 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=66fbfe1297997a3f6b2181cd723816150ad2453527c7cab6c83a9c67b9af2478
+register_shell="/bin/nu"
+
+case "$XBPS_TARGET_MACHINE" in
+	armv* | aarch64*)
+		hostmakedepends+=" python3" ;;
+esac
+
+pre_build() {
+	case "$XBPS_TARGET_MACHINE" in
+		armv* | aarch64*)
+			vsed -i '91s/"bson", //' Cargo.toml ;;
+	esac
+}
+
+do_check() {
+	: # cargo tests fail with argument --target
+}
 
 post_install() {
 	vlicense LICENSE

  parent reply	other threads:[~2021-02-04  8:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 18:33 [PR PATCH] " FollieHiyuki
2021-01-30 18:34 ` FollieHiyuki
2021-01-30 18:37 ` [PR PATCH] [Updated] " FollieHiyuki
2021-01-30 18:40 ` FollieHiyuki
2021-01-30 18:44 ` FollieHiyuki
2021-01-30 18:45 ` FollieHiyuki
2021-01-30 18:47 ` FollieHiyuki
2021-01-30 19:29 ` [PR PATCH] [Updated] " FollieHiyuki
2021-01-30 19:58 ` FollieHiyuki
2021-01-31  0:33 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-04  5:40 ` ahesford
2021-02-04  5:45 ` ericonr
2021-02-04  5:47 ` ericonr
2021-02-04  6:35 ` FollieHiyuki
2021-02-04  6:55 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-04  6:58 ` FollieHiyuki
2021-02-04  8:15 ` FollieHiyuki [this message]
2021-02-06  5:40 ` ericonr
2021-02-06  6:42 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-06  6:47 ` FollieHiyuki
2021-02-06  6:50 ` FollieHiyuki
2021-02-06  6:54 ` FollieHiyuki
2021-02-06  7:01 ` FollieHiyuki
2021-02-06  7:02 ` FollieHiyuki
2021-02-06  7:10 ` FollieHiyuki
2021-02-14 21:26 ` ericonr
2021-02-14 23:17 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-15 18:40 ` FollieHiyuki
2021-02-15 18:53 ` ericonr
2021-02-16  6:27 ` [PR REVIEW] " ericonr
2021-02-16  6:27 ` ericonr
2021-02-16  6:27 ` ericonr
2021-02-16 11:33 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-16 11:38 ` [PR REVIEW] " FollieHiyuki
2021-02-16 11:41 ` FollieHiyuki
2021-02-16 11:42 ` FollieHiyuki
2021-02-16 17:43 ` [PR PATCH] [Updated] " FollieHiyuki
2021-02-16 17:45 ` FollieHiyuki
2021-02-16 17:56 ` [PR REVIEW] " FollieHiyuki
2021-02-16 18:11 ` [PR PATCH] [Merged]: " ericonr

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=20210204081512.JMR5PPPA_60S9XC22LD4YOOMDaDGUN2UfcTc4DdAdck@z \
    --to=folliehiyuki@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).