Package Details: powershell 6.0.0.beta.3-2

Git Clone URL: (read-only)
Package Base: powershell
Description: A cross-platform automation and configuration tool/framework (latest release)
Upstream URL:
Keywords: microsoft powershell shell
Licenses: MIT
Conflicts: powershell-git
Submitter: jsteel
Maintainer: kylesferrazza
Last Packager: kylesferrazza
Votes: 14
Popularity: 3.389450
First Submitted: 2016-11-26 22:16
Last Updated: 2017-07-22 02:28

Dependencies (5)

Required by (0)

Sources (4)

Latest Comments

kylesferrazza commented on 2017-07-21 22:09

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

Jristz commented on 2017-07-19 05:42

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

kylesferrazza commented on 2017-06-09 18:59

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

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

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

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

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

Sacro commented on 2017-06-07 15:55

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.

kylesferrazza commented on 2017-06-07 11:46

So are suggesting I go back to the last alpha?

Sacro commented on 2017-06-07 11:32

This is a beta release, not a stable release (and also brings in dotnet-cli-git), please move it to a powershell-beta package.

All comments