A tool to ease your package managing needs, all with the goodness of the terminal! Still a WIP!
Basic tasks — installing, removing, and searching for packages — are already usable.
Tired of typing commands? Me too, I groan in pain when I have to write another command. I also hate dealing with GUI app stores, they take forever to load (I'm looking at you KDE Discover). So what should I do? Just smush the two together! The Package Dealerer (name being worked on.) guides you through everything, and all you do is select buttons and type in the package names.
This is a Bash script. So you need Bash (duh). It also won't deal with .dmg files (because those don't have a CLI, as far as I know) so you can only use MacPorts and Homebrew on Macs.
Just download the scripts (each and every one of them!), place them in the same directory, and run chmod +x on each script! Yes, it's annoying that you need to run a command on each of these, but it's a security thing, so you have to. Maybe some of you won't have to do this, it's a weird world of permissions we live in. You can add them to your $PATH too, if you'd like. By the way, you need to have gum installed (best to install it using brew), otherwise literally nothing will work.
Previously, it only worked with DNF, Flatpak and Homebrew out of the box. You could have changed those by editing the commands used in the scripts, but you had to do that to ALL the scripts, and that's just dumb. Now, it still only works with those three out of the box, but you can now change those from one place, which is dealwithpkgs.sh. All the commands are set as variables, and they're right at the top of the script with comments telling you what they do. So all you need to do is open that one file, read through it, and change the commands. Sure, it could be easier, but this is just a project to help me learn Bash for the first time, and I don't know much at the moment.
It uses variables to determine what commands to run for each action, but you still have to edit dealwithpkgs.sh. It's easier than editing the commands in each and every script here; but it's still 'complex' to the beginning Linux user — you can't expect a Windows or Mac user to edit a simple script — and I should probably look for a way to simplify this editing thing. There could be alternatives though, like uploading multiple versions of the script for various distros, which would also solve the problem with the special guidance.
The thing requires multiple seperate scripts because it was messing with me when I tried it. That was back when I used nano (I'm probably gonna get bombarded with 'I use Vim' messages somehow). Maybe I can streamline it by reducing the amount of scripts, for example putting the functions of 'pkgsinstflatpak.sh' straight into 'pkgsinst.sh'.
Perhaps I could also make it so that it will install Flatpak, Snap (lol no) or Homebrew if not installed.