5 ms·
> a more comprehensive package manager like apt or dnf I don't see how apt or dnf are any more comprehensive than pacman. What do you mean by that? Before Arc
by matheusmoreira 5y ago
> a more comprehensive package manager like apt or dnf
I don't see how apt or dnf are any more comprehensive than pacman. What do you mean by that?
Before Arch, I used Fedora. It used yum as its package manager. That thing managed to corrupt its own databases at least twice during normal usage. Distribution major version upgrades always caused problems.
I never had problems like these after switching to Arch.
> I don’t mind compiling programs myself when needed
You only need to compile user packages. Official Arch Linux repositories host binary packages. You can download the PKGBUILD if you want.
> for most things I’m happy to not have to hand-hold my OS when it comes to updates.
99% of the time updates just work for me. Sometimes they introduce a few .pacnew files, I diff and merge them with my local files and that's it.
> Like… why?
Sometimes manual intervention is necessary. Usually it's not a big deal. The news tell you what to do and most importantly why you must do it.
The most complicated maintenance I ever experienced with Arch was when it switched /bin to /usr/bin.
- diffeomorphism 5y agoNot PP, but to me it means much less manual intervention/more hooks etc. . For instance, for debian I can just turn on automatic updates and basically never need manual intervention. For arch I am not supposed to use automatic updates and have to (!) read the news. Why? Why does arch need more manual intervention? Sure, I can do that but it just seems like a pointless waste of time.
- m01 5y agoI don't think Debian's automatic updates do major release upgrades automatically, do they? Those IIRC do require manual intervention - if nothing else you need to run the installer & possibly respond to prompts, but possibly more depending on your system.
- pxc 5y ago> I don't think Debian's automatic updates do major release upgrades automatically, do they? Those IIRC do require manual intervention For major release upgrades, the official upgrade procedure is to follow instructions like these: https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html https://www.debian.org/releases/stable/amd64/release-notes/c... So yeah, you have a somewhat manual upgrade process once every two years, if you're not on one of the rolling release (‘testing’ or ‘unstable’). On the other hand, you do get to choose when you make those updates. You don't get caught by surprise with them because you forgot to read the news. Debian's documentation on Testing and Unstable[1] contains some snippets that may feel familiar to Arch users, including this very relevant bit: > Consider (especially when using unstable) if you need to disable or remove unattended-upgrades in order to control when package updates take place. — https://wiki.debian.org/DebianUnstable#What_are_some_best_practices_for_testing.2Fsid_users.3F https://wiki.debian.org/DebianUnstable#What_are_some_best_pr...
- matheusmoreira 5y ago> For instance, for debian I can just turn on automatic updates and basically never need manual intervention. I question what sort of updates you're actually getting. Debian is known for being extremely outdated. This is a major reason for its stability. Sometimes things change way too much. Sometimes they change in incompatible ways. Sometimes changes come from upstream and there's nothing the distribution can do about it. In these cases, our attention is required. Things break and we need to fix them. We need to adapt. In order to avoid this, Debian must be outdated. It must avoid updates that break things and this necessarily means you end up using software that's years old. That's fine, it's a perfectly valid trade-off. I'm sure there are a lot of users out there whose wants and needs are perfectly filled by Debian. If someone's interested in Arch, it's likely because of its huge repository of up-to-date unpatched software. The Arch user must be able to deal with change. Sometimes it's unavoidable and Arch culture makes it clear that users are expected to put such effort into their systems.
- diffeomorphism 5y ago> years old. where years<=2. Not a big deal, but yes can be annoying. That said upgrades between major versions are also usually automated and well tested (since they have lots of time to prepare and test that). > users are expected... The difference is what is considered "unavoidable". In particular, on other distros packagers are supposed to ... and only if that is not possible users are supposed to ...
- pxc 5y ago> I don't see how apt or dnf are any more comprehensive than pacman. What do you mean by that? In terms of the core functionality of package managers, they both have more robust dependency resolvers (and dnf's is actually complete[1]). In the case of dnf, it's also more ‘comprehensive’ in the sense that the singular CLI tool handles more package management functionality (e.g., it includes repo management), and in the sense that it supports plugins. They're also both more comprehensive in the sense that you don't need to resort to one of a dozen third-party ‘wrappers’ in order to use the bulk of packages available in those distros' ecosystems. — 1: See the discussion of completeness here: https://arxiv.org/pdf/2011.07851.pdf https://arxiv.org/pdf/2011.07851.pdf
- matheusmoreira 5y ago> they both have more robust dependency resolvers (and dnf's is actually complete[1]) > 1: See the discussion of completeness here: https://arxiv.org/pdf/2011.07851.pdf https://arxiv.org/pdf/2011.07851.pdf That's interesting. In what ways are these resolvers superior to pacman? I never had dependency resolution issues. Can you help me understand with concrete examples? Pacman is not cited anywhere on that paper. > you don't need to resort to one of a dozen third-party ‘wrappers’ in order to use the bulk of packages available in those distros' ecosystems Are you referring to the AUR? I believe that's more of a man power issue. Arch is a smaller project compared to the other major distributions. There aren't enough maintainers for all packages.
- pxc 5y ago> That's interesting. In what ways are these resolvers superior to pacman? One good example is that even though PKGBUILDs can contain version constraints (see an example here[1]), that metadata is not always present and so it is underutilized. Pacman doesn't support ‘partial upgrades’[2] (once you refresh your package lists, installing anything is ‘unsupported’ until you upgrade everything), and this is why. (I also think that paper's notion of ‘completeness’ could probably be enriched somehow, because I've seen situations where `apt-get` will crap out but `aptitude` will offer a ‘compromise’ solution which involves downgrading some packages or removing some, and generally package managers based on libsolv do even better IME. Here Arch likely falls flatter.) Another depsolver related issue in Pacman (related to the lack of partial upgrades) is the lack of distinction between upgrades and dist-upgrades. In apt and dnf, upgrades are non-destructive by default, meaning that they don't offer solutions that involve removing or downgrading user-selected packages. Pacman has no such distinction. > I never had dependency resolution issues. Can you help me understand with concrete examples? One fairly common case is that Arch just ignores the dependencies of AUR-installed packages at install time, freely upgrading packages without respect to reverse-dependencies that aren't declared in a repo.[4] Hence, ‘if packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries’... every single time you upgrade, if you've installed anything from the AUR, it can leave your system with broken packages. Apt and dnf, in contrast, treat every package you install the same way. Additionally, Arch packages don't always declare version constraints for their library dependencies, and there's no CI that tests for ABI changes (there is some in Debian, although such tools can't work perfectly). So you have to use another tool (apparently one popular choice is some script from the Arch forums in 2005, lol[5]) to scan for such breakages, or else just discover them when packages don't work. On the other hand, when Arch does consider the version constraints of installed packages, the lack of partial upgrades can be problematic for downstream distros. Any version constraints placed by downstream repos on dependencies shared with upstream can just leave you totally unable to upgrade anything at all for a while.[6] — 1: https://github.com/archlinux/svntogit-packages/blob/master/dbus-sharp-glib/trunk/PKGBUILD#L11 https://github.com/archlinux/svntogit-packages/blob/master/d... 2: https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported https://wiki.archlinux.org/title/System_maintenance#Partial_... 3: https://wiki.archlinux.org/title/Pacman/Rosetta#Basic_operations https://wiki.archlinux.org/title/Pacman/Rosetta#Basic_operat... 4: https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages https://wiki.archlinux.org/title/Arch_User_Repository#Instal... 5: https://bbs.archlinux.org/viewtopic.php?id=13882 https://bbs.archlinux.org/viewtopic.php?id=13882 6: https://superuser.com/questions/1497098/pacman-unable-to-update-since-it-breaks-dependency-with-itself https://superuser.com/questions/1497098/pacman-unable-to-upd...