Awk (as gawk) and iproute2 are part of a base arch install. There's no need to install them separately.
Arch Packages You Might Want to Install
11–20 of 25 posts
Re: Arch Packages You Might Want to Install
#12Screw it, just pull in the entire default repo and call it a day. With how cheap disk space is now, I wonder how infeasible this would actually be. How much disk and bandwidth would this take for, say, Ubuntu, or Arch, or Arch plus the AUR? Once everything is installed, the package manager could handle incremental updates rather painlessly if you ran them often enough. Conflicting packages might pose a bit of an issu…
Per https://wiki.archlinux.org/title/DeveloperWiki:NewMirrors a full mirror of the arch repos would be over 50 GiB. AUR would be impossible to tell, as you have to grab sources and build it yourself. I'd imagine fairly massive though.
I can only really speak for arch as that's what I'm familiar with, but I'd imagine the mirrors would not be happy about all the wasted bandwidth. The whole idea sort of seems unnecessary to me.
Re: Arch Packages You Might Want to Install
#13Screw it, just pull in the entire default repo and call it a day. With how cheap disk space is now, I wonder how infeasible this would actually be. How much disk and bandwidth would this take for, say, Ubuntu, or Arch, or Arch plus the AUR? Once everything is installed, the package manager could handle incremental updates rather painlessly if you ran them often enough. Conflicting packages might pose a bit of an issu…
Per https://wiki.archlinux.org/title/DeveloperWiki:NewMirrors a full mirror of the arch repos would be over 50 GiB. AUR would be impossible to tell, as you have to grab sources and build it yourself. I'd imagine fairly massive though. I can only really speak for arch as that's what I'm familiar with, but I'd imagine the mirrors would not be happy about all the wasted bandwidth. The whole idea sort of seems unnecessar…
What about pulling in binary packages the first time you try to run them. Or pulling in shared library packages the first time an app tried to load them.
Re: Arch Packages You Might Want to Install
#14That’s a nice list, but a brief explanation for each package would be very helpful. As a beginner I have no clue what most of them do. I chose Arch because I do not want to fill up my system with software I never use, copy pasting this list would defeat the purpose…
Re: Arch Packages You Might Want to Install
#15This is very bad advice. The point of Arch is to install what you need because you have learned why you need it.
Installing random packages because an Internet blog says you should? Many of these are specific to what choices you have made on your computer.
Re: Arch Packages You Might Want to Install
#16That’s a nice list, but a brief explanation for each package would be very helpful. As a beginner I have no clue what most of them do. I chose Arch because I do not want to fill up my system with software I never use, copy pasting this list would defeat the purpose…
I have no Arch system at hand, but isn't that what pacman -Si would do?
curl | xargs -n 1 pacman -Si
DRY, don't type what can be generated.
Re: Arch Packages You Might Want to Install
#17Screw it, just pull in the entire default repo and call it a day. With how cheap disk space is now, I wonder how infeasible this would actually be. How much disk and bandwidth would this take for, say, Ubuntu, or Arch, or Arch plus the AUR? Once everything is installed, the package manager could handle incremental updates rather painlessly if you ran them often enough. Conflicting packages might pose a bit of an issu…
There’s going to be a lot of duplication in AUR. Also a lot of package that don’t build too.
Re: Arch Packages You Might Want to Install
#18pulseaudio should be replace pipewire and sudo by doas I would also add: - htop - mc - fish (or zsh) - yay (from aur)
How do you fully replace sudo with doas on Arch? A bunch of packages depend on sudo, including glibc, and it's not obvious to me that they don't depend on the specific /usr/bin/sudo command being available.
Re: Arch Packages You Might Want to Install
#19This is just a list of packages the author uses and isn't even specific to Arch. I am not sure it is actually useful to anyone.
Re: Arch Packages You Might Want to Install
#20This is very bad advice. The point of Arch is to install what you need because you have learned why you need it. Installing random packages because an Internet blog says you should? Many of these are specific to what choices you have made on your computer.
I have a list of explicitly installed packages through pacman, put it in a plaintext file, and then install those on a new Arch Linux that is supposed to be used for desktop use.
The most issues I have is related to Nvidia drivers because I need an old one. I think it is from AUR as well.