Ubuntu: sudo apt-get install software-properties-common; sudo add-apt-repository ppa:some/repository(Run the second command for every new software not found in the official repos)
Arch: sudo pacman -S git;git clone https://aur.archlinux.org/yay-git;cd yay-git;makepkg -si(No need to do anything again. Almost every software is found in the AUR)
That's interesting, WARNING HERE BE DRAGONS( i.e. my opinion lol)
I find apt a lot easier, because I'm typing out the verb that I want to happen. With pacman it's all flags, so you have to memorize all those flags instead of just thinking about what you're trying to do.
I also I have an update script that I wrote for Debian based systems to handle update/upgrade/dist-upgrade and what not, that sure id never run on production systems but it's served me well for years.
That way my upgrade process is just "updatey" (yes the y means auto accept lol)
Also as far as additional repos go I think I've only got like 2 on Debian based machines, so I don't feel like that's a big deal.
I also always found it strange that pacman basically needs wrappers (such as yay) to do the same functionality that the other package managers do out of the box. Now sure, you don't need to use yay, but it's gonna get painful if you don't.
I always liked the Arch and Arch based distros, because:
Ubuntu:
sudo apt-get update && sudo apt-get upgrade
Arch:
sudo pacman -Syu
Ubuntu:
sudo apt-get install software-properties-common; sudo add-apt-repository ppa:some/repository
(Run the second command for every new software not found in the official repos)Arch:
sudo pacman -S git;git clone https://aur.archlinux.org/yay-git;cd yay-git;makepkg -si
(No need to do anything again. Almost every software is found in the AUR)Ubuntu:
sudo apt-get install ...
Arch:
pacman -S ...
That's interesting, WARNING HERE BE DRAGONS( i.e. my opinion lol)
I find apt a lot easier, because I'm typing out the verb that I want to happen. With pacman it's all flags, so you have to memorize all those flags instead of just thinking about what you're trying to do.
I also I have an update script that I wrote for Debian based systems to handle update/upgrade/dist-upgrade and what not, that sure id never run on production systems but it's served me well for years.
That way my upgrade process is just "updatey" (yes the y means auto accept lol)
Also as far as additional repos go I think I've only got like 2 on Debian based machines, so I don't feel like that's a big deal.
I also always found it strange that pacman basically needs wrappers (such as yay) to do the same functionality that the other package managers do out of the box. Now sure, you don't need to use yay, but it's gonna get painful if you don't.
You're right about Pacman being a little bit cryptic, but I think you could solve it using aliases.
Really cool what you did with your script 😄
To pacman's credit though..
man pacman
leads to some very well written documentationSo your dragons are a bit more powerful 😜
You're right! I always thought that the ubuntu way of installing packages was “ok” until I started using pacman.