Hacker News new | ask | show | jobs
by majewsky 3076 days ago
> You guys really have less trouble with package managers than Windows installers?

Hell yeah. I remember when I had to set aside entire weekends to reinstall a Windows machine. These days, when I need to reinstall one of my Linux boxes, I just fire up the Arch installer, and instead of installing the "base" package group as the manual instructs you, I install my configuration package for that machine which pulls in all applications (from the kernel and coreutils all the way up to Steam) and contains all configuration. When I recently reinstalled my notebook to enable full-disk encryption, it took me around 30 minutes, of which most time was spent downloading packages, and downloading /home from the backup storage. Net working time was maybe 5 minutes. I actually watched a movie while doing it.

The issues that you're seeing are because the particular package manager you encountered is shit. (Or rather, because Debian's/Ubuntu's byzantine packaging processes create a ton of pathological cases.) I've never had such problems on Arch. (Except for those cases about once a year when they restructure something and the package manager is confused, in which case you go to archlinux.org and the most recent news item contains the magic shell incantation that immediately resolves the issue.)

3 comments

> I just fire up the Arch installer

I will concede that I usually run into far fewer problems/bugs with Arch's pacman than Ubuntu's apt/dpkg. It seems far more robust, and honestly more intuitive too. On the other hand, (1) getting things set up in Arch in the first place is so much more of a pain that it wastes just as much time, and (2) I have also had bad luck with Arch, when after re-downloading and re-trying the install a couple times, I finally realized the ISO I downloaded just had a broken build. (?) I would follow the setup instructions (yes, the appropriate ones, I know they change over time) but pacman would just somehow choke by the end. Once I realized it was a problem with their build I just went back to an earlier ISO and updated and it was fine. But yes, overall, I've had far better experiences with it.

> I just fire up the Arch installer

When I switched to Linux full time, I basically replaced Ninite with a one line shell script and was done. It also removes any worry that Ninite might go sour in the future.

One wonders why you have to rebuild your "better than reinstalling Windows all the time" system so often as to have invested the time creating a metapackage of your configuration.
1. Because the package acts as a backup, and the commit history explains why I set up stuff the way I did.

2. Because it's really convenient to just link people to its Github repo when they ask questions like "how do you configure MPD to use PulseAudio?".

Wow but that sounds like a problem created solely for the sake of the solution.