/docs/pak/Recent content in Pak Docs onHugo -- gohugo.ioen-US/docs/pak/configuration/Mon, 01 Jan 0001 00:00:00 +0000/docs/pak/configuration/Config file Pak uses a custom config file at /etc/pak.cfg. For example, this is what the apt config looks like: # Write the name of the package manager in all lowercase below apt # Write a comma separated list of commands from the manager below install,remove,update,upgrade,search,download # Write "yes" or "no" depending on whether you want to use root yes # Write command to use for root sudo # Write a comma separated list of shortcuts below rm,inst # Write a comma separated list of shortcut mappings from the manager below remove,install This file is read by pak to tell it what to do./docs/pak/installation/Mon, 01 Jan 0001 00:00:00 +0000/docs/pak/installation/Using precompiled binary Pak uses continuous integration to compile. You can find the binary by clicking the download badge above. Using the AUR If you are running an arch-based linux distro, you can use the Arch User Repository to install pak. First, make sure the yay AUR helper is installed, then run the following: yay -S pak Building from source Downloading Pak is hosted on my Gitea instance. If that is down, it is also mirrored on Gitlab./docs/pak/usage/Mon, 01 Jan 0001 00:00:00 +0000/docs/pak/usage/Using pak is simple, just run pak and one of the commands from the config file. Pak understands partial commands, so these commands will be identical: pak in <package> OR pak inst <package> OR pak install <package> The lack of sudo is intentional. Pak will not allow running from root by default as it already invokes root internally. To bypass this, simply give pak the -r flag. Using shortcuts in pak is just as simple as commands, just run pak and a shortcut, like this: