Package Details: powershell-git 6.2.0.rc.1.197.gceed73d73-1

Git Clone URL: https://aur.archlinux.org/powershell-git.git (read-only)
Package Base: powershell-git
Description: A cross-platform automation and configuration tool/framework (git version)
Upstream URL: https://github.com/PowerShell/PowerShell
Keywords: microsoft powershell shell
Licenses: MIT
Conflicts: powershell
Provides: powershell
Submitter: qrwteyrutiyoup
Maintainer: kylesferrazza
Last Packager: kylesferrazza
Votes: 21
Popularity: 0.009072
First Submitted: 2016-08-21 20:35
Last Updated: 2019-04-24 18:39

Pinned Comments

kylesferrazza commented on 2017-10-26 17:49

Note that the binary is now called "pwsh"

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

kylesferrazza commented on 2017-04-29 13:27

Fixed and updated to work with dotnet 2.0!

the_lf commented on 2017-04-10 01:59

Also can confirm @drizzt396's issues. 3000+ errors.

the_lf commented on 2017-04-10 01:57

This actually depends on dotnet-sdk, which isn't listed in the pkgbuild.

drizzt396 commented on 2017-03-29 11:54

Holy shit, the makepkg used fail gracefully on one of my machines (compiles fine on my other box), and now it just vomits errors (3764 before I managed to interrupt). What happened?

jsteel commented on 2017-02-16 08:26

Ignore my last comment; I think for this package I didn't chroot as it gave me an issue, so yes I see those files in my home (not part of the package but they are created).

jsteel commented on 2017-02-16 08:17

I hadn't noticed as I build in a chroot. I'll take a look but in the meantime any suggestions welcome.

Synthead commented on 2017-02-16 00:50

Building this package puts a lot of junk in ~/.nuget. Can we specify a different path so that the user's home doesn't get unwanted files during the build?

jsteel commented on 2016-12-22 22:49

I think I had that error, but rebuilt all deps (including dotnet-cli deps) and it built OK then.

C0rn3j commented on 2016-12-22 21:16

Fails to build
http://pastebin.com/4XWEVsR3

rahool commented on 2016-12-07 04:16

Yes, dotnet-bin. There was an issue with dotnet-cli for which an interim patch has been provided, so this is no longer a problem.