Package Details: powershell 7.4.1-4

Git Clone URL: https://aur.archlinux.org/powershell.git (read-only, click to copy)
Package Base: powershell
Description: A cross-platform automation and configuration tool/framework (latest release)
Upstream URL: https://github.com/PowerShell/PowerShell
Keywords: .net automation microsoft net powershell script scripting shell
Licenses: MIT
Submitter: jsteel
Maintainer: kylesferrazza (richardba, carsme)
Last Packager: carsme
Votes: 83
Popularity: 0.026487
First Submitted: 2016-11-26 22:16 (UTC)
Last Updated: 2024-03-10 11:11 (UTC)

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 Next › Last »

<deleted-account> commented on 2017-08-17 04:44 (UTC)

well @kylesferrazza dotnet 2.0 was released, powershell build now with beta5?

kylesferrazza commented on 2017-07-21 22:09 (UTC) (edited on 2017-07-22 02:09 (UTC) by kylesferrazza)

I'll update to beta 4 as soon as dotnet 2.0 preview 3 is released and add an entry to /etc/shells tonight

<deleted-account> commented on 2017-07-19 05:42 (UTC)

is possible to add /usr/bin/powershell to /etc/shells like the other shells? I'm using it but I was forced to add manually the entrie but I would preffer keep it tracked on the package like fish or zsh do Also there is beta-4 released 5 days ago https://github.com/PowerShell/PowerShell/releases

kylesferrazza commented on 2017-06-09 18:59 (UTC) (edited on 2017-06-09 19:03 (UTC) by kylesferrazza)

@Sacro https://aur.archlinux.org/packages/powershell-dotnet_stable This package will continue to use dotnet-cli-git as it should represent the latest powershell release. Powershell-dotnet_stable will contain the last release of powershell that works with the latest release of dotnet.

Sacro commented on 2017-06-08 21:24 (UTC)

Right, so then I guess this should remain as powershell, with dotnet-cli, and a new package should be created (powershell-beta?) that pulls in dotnet-cli-git. Sorry to be a pain.

kylesferrazza commented on 2017-06-08 12:35 (UTC)

@Sacro The problem with linking against dotnet-cli is that the latest PowerShell releases rely on dotnet 2.0, and a stable release of dotnet 2.0 hasn't been made yet.

Sacro commented on 2017-06-08 10:59 (UTC)

My main issue was that you're wanting to pull in dotnet-cli-git, this should be done in a separate package so that those of us wanting to keep dotnet-cli to stable releases can. I didn't realise there was no current "stable" non-beta release, that's fine, but can you link it against dotnet-cli instead?

kylesferrazza commented on 2017-06-07 17:11 (UTC) (edited on 2017-06-07 17:12 (UTC) by kylesferrazza)

@Sacro It's not a non-alpha package.. There haven't yet been "stable" non-beta releases.

Sacro commented on 2017-06-07 15:55 (UTC)

Eugh, just noticed that you're pushing alpha builds in a non-alpha package. Yes, I guess so, (or whatever so long as it doesn't require dotnet-cli-git). Ideally you'd have separate PKGBUILDs for the differing versions. My main issue is I need dotnet-cli, not dotnet-cli-git.

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 Next › Last »