19
Do not update single packages on Archlinux, but
(beehaw.org)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
No,
pacman -S package
is safe. Because the package list is not updated this way, and therefore the system is not updated and nothing else is affected. New packages can be installed with this command, perfectly okay. That is in the spirit of Archlinux.I think my idea would not work because the nature of the command
-S package
, as no new version would be synced. This is not a partial upgrade and it does not need to be discouraged.If the package is not in your cache, it needs to download it from the remote server first. The version on the remote server is built against the dependencies on the remote server. So if your local dependency is older, it will be a partial update!
No, because
pacman -S
will use the current package list.And where does it download the newly installed package from? It's not in your cache, because you haven't had it installed before and the remote server only has the newest version.
I guess that's the key takeaway for me from this post and replies.