Having options is what Linux is about and not one thing is for everyone. But learning about them can't possibly be a bad thing. If you can't see any use of a GUI Package manager, especially when first starting out, then that's your opinion. I don't and didn't recommend blindly using it to install each and every package, I simply said to check it out and that I use it for quick updates. In my opinion you should experiment and a GUI makes it easier & faster to do so. You can't possibly know each and every program by name when you are starting out. So I could try out new programs, figure out what I liked. I used it for browsing when I first started, well I used other Package managers on other distros to do that. Автор сообщения: CoreFaster if you know the name of what you are looking for maybe. Here is a good comparision which command translates to the same command on other package managers. You'll find out that it's a lot simpler and faster than apt which often requiers multiple commands to do the same thing. pacman syntax is dead simple and doesn't need any GUIs. If you don't read the pacman output you'll run into trouble sooner or later. Some of them are handled with "echo SomeText" some cat "SomeText" so it's hard for GUIs to parse them. They can contain instructions to be displayed after removal, upgrade, installation etc. Like for the vbox-host-modules that will get installed with virtualbox: You'll find these messages in simple bash scripts as *.install files of that particular packages. Now if you install the same package with a GUI you'll miss this and try to start virtualbox and wonder why it doesn't work and start cursing Arch and go to the wiki and spend 15 minutes doing something that is totally unnecessary, when all you had to do is to read the output. "=> You must load vboxdrv module before starting VirtualBox: You install virtualbox with pacman -S virtualbox. The pacman output will tell you if there is anything else you'd have to do or if there are pacnew and pacsave files that have to be merged or what optional dependecies there are. Most of them hide any output from you which makes them borderline useless.
Some people just don't care about the technical beauty of Arch and it's flexiblity and want something else from a distro which is ok, too. It takes some time to learn but it's very rewarding if you are the right person for Arch Linux. It certainly isn't for everyone and if something doesn't work it most likely isn't the distros fault. I think the best tip for a new Arch Linux user is to have patience. You might also need it for Skype and Wine which is also only available as 32 bit.
If you install i686 Arch Linux you'll install 32 bit versions for everything anyway and won't need multilib. If you need the 32 bit version like 32 bit flashplugin for Steam to watch videos you'll install lib32-flashplugin and it will get pulled from.
If you are using x86_64 architecture you'll always pull the 64 bit version of every that is available for 64 bit. After a while you'll see that multilib is much better than on Debian distros. Arch will only install what's absolutely needed.
That's why the 32 bit driver is in the repo and has to be installed speparately, since it's not strictly needed by the "regular" driver. That's probably something that you're not used to from Debian/Ubuntu based distros. It's always good to check out the packages on the archlinux package database:Įarlier the libGl.so was part of the nvidia-utils package, but it was split up to be more consistent with the other packages like mesa-libgl.Īrch Linux keeps 32 bit and 64 bit strictly separate. So installing "nvidia" is enough to get the newest driver since it will pull in nvidia-libgl and nvidia-utils. Now if you install the kernel module "nvidia" it depends on all the other packages otherwise it wouldn't work.
You'd need a kernel module (comes with the "nvidia" package), the nvidia helper utilites like nvidia-smi, nvidia-settings, nvidia-xconfig (comes with "nvidia-utils") and the vendor specific OpenGL library (libGl.so) (comes with "nvidia-libgl"). Let's take the mainline branch of nvidia. Yes, you have to keep in mind the dependencies.