Closed freed00m closed 3 years ago
there are multiple ways of running pacui:
installing it from AUR or manjaro repo
downloading the "pacui" file and running it as described in https://github.com/excalibur1234/pacui#execute-without-prior-installation
downloading the "pacui" file from github, and executing the following lines in the download directory (this is what the "installation" of pacui does):
chmod +x pacui
sudo cp pacui /usr/bin/
pacui
downloading the "pacui" file from github, and executing the following lines in the download directory:
chmod +x pacui
pacui
you are suggesting to change the file permissions of "pacui" file. sadly, i cannot see what the new file permissions are. i would suggest permission level 744. i have just pushed a commit, which does exactly that.
however, the problem probably continues, because curl, wget, etc do not copy/download a file (including file permissions), but only the content of the file. the permissions for this file are taken from umask as can be read here: https://unix.stackexchange.com/questions/82578/why-is-that-when-i-download-a-binary-from-the-web-it-doesnt-have-executable-per
this means that downloading the "pacui" file from github gives you an executable file, but downloading the "pacui" file with curl/wget does probably NOT give you an executable file.
i have not tested this behavior thoroughly, though.
do you think my latest commit solves the problem (partially) or do you recommend a different permission level?
Yes
This was basically this commit and what I did :)
chmod +x pacui
The info is in inode and is visible in the commit patch and even on github.
Btw you can't install it from AUR, that was the whole point. Having pacui as a submodule somewhere :) It's not in Arch repository either.
Ok hear me out, I am thinking since the script is not allowed to live inside AUR, the next best thing is to get it from git straight away.
Making then a short symling somehere on PATH is easy so we could easily launch
$ pacui
instead of$ bash pacui