Search Criteria
Package Details: powershell 7.4.1-4
Package Actions
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: | 84 |
Popularity: | 0.35 |
First Submitted: | 2016-11-26 22:16 (UTC) |
Last Updated: | 2024-03-10 11:11 (UTC) |
Dependencies (9)
- dotnet-runtime-8.0 (dotnet-runtime-8.0-binAUR, dotnet-runtime)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- dotnet-sdk-8.0 (dotnet-sdk-8.0-binAUR, dotnet-sdk) (make)
- git (git-gitAUR, git-glAUR) (make)
- unzip (unzip-natspecAUR, unzip-zstdAUR) (make)
- inetutils (inetutils-gitAUR, busybox-coreutilsAUR) (check)
- iputils (busybox-coreutilsAUR, iputils-gitAUR) (check)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR) (check)
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 19 Next › Last »
kylesferrazza commented on 2019-11-29 13:23 (UTC)
@DDoSolitary Can you link to the issue you opened upstream?
DDoSolitary commented on 2019-11-29 13:20 (UTC)
@user981257923 I've already opened an issue in the upstream repo (#33), but unfortunately haven't got any response yet and the repo doesn't seem to be actively maintained. A simple way to work this around would be removing the
-Werror
flag in CMakeLists.txt of that project. However, it is not very ideal because the code will eventually get broken after glibc removes that header.user981257923 commented on 2019-11-29 12:45 (UTC) (edited on 2019-11-29 12:48 (UTC) by user981257923)
Log:
Any way to fix this which doesn't involve upstream?
Case_Of commented on 2019-11-29 11:17 (UTC)
Hello, How to fix the following issue?
marcoh00 commented on 2019-11-05 20:18 (UTC)
I'm unable to build this package (6.2.3-1) - the build() step always fails with:
Is anyone else experiencing the same problem?
kylesferrazza commented on 2019-10-28 17:12 (UTC)
@skypixel
I agree it would make sense to package OneGet with this package. I am currently working on adding it to the build. I would appreciate a patch if you have the time to work on it before I get to it.
DDoSolitary commented on 2019-10-27 17:21 (UTC)
Hello, I'm unable to run pwsh after building&installing this package. It says:
skypixel commented on 2019-10-13 09:58 (UTC)
For those wondering, Install-Module doesn't work because OneGet is not included in this package (see https://github.com/PowerShell/PowerShell/issues/6472#issuecomment-375997500 ). @kylesferrazza is there any reason why OneGet is not included? Wouldn't it make sense to make it available since it's the main means to install external modules?
kylesferrazza commented on 2019-09-12 21:34 (UTC) (edited on 2019-09-12 21:44 (UTC) by kylesferrazza)
@agowa338
That patch breaks the build for me:
agowa commented on 2019-07-28 23:09 (UTC)
The wrong folder gets copied, therefore some dependencies are fetched from the nuget cache after the package is installed. If you now try to run pwsh from any other user it will fail, as the nuget cache is no longer accessible (belongs to the build user). Same happens if you move the final package to a remote system, install and try to run it. (The global‑packages cache is located at ~/.nuget)
This can be fixed by:
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 19 Next › Last »