Why would you use 4 package managers to do 1 thing ? Most people who use arch use 1 and it does the job. All of them are built around pacman + smth for AUR packages. Personally I use pacui. Why would you convert package from other distro, if another distro has it then it most certainly exists in the AUR, never once had to touch another distro's packaging.
I don't know about the "the modder's distro" part but I personally had much less headaches with it than I had with Ubuntu,fedora,debian, and CentOS.
The only thing that sucks for me (regardless of distro) is Nvidia updates.
A lot of software packages I've been using lately don't exist in the AUR. My tastes might be more niche than yours, I don't know.
> Why would you use 4 package managers to do 1 thing ?
Because all the software I'm trying to install has documentation like "install with pacman" or "install with pamac" or "install with yay" or "install from source" or "install from AUR" or... I think you get where this is going.
> Your experience sounds weird. Reading it remind me of people who come from programming paradigm X try paradigm Y and only use methods from X only to conclude that Y sucks.
Reading your rebuttal to my experience reminds me of people who answer questions on Stackoverflow like, "why would you do it this way? Your question isn't valid, your question _should have been_..." That is to say, rather than attempt to understand where I'm coming from, you thought to overwrite my experience with your own, as if yours is the truer experience to be had. My time using Arch and Arch-variant distros led me to having a seemingly fragmented experience over where to find software. That's got nothing to do with X being better than Y, it has more to do with X being mostly one or two overall places to find software, and Y being fragmented between 4-5 + conversions between apt/yum packages and PKGBUILD scripts. I'm not saying Y is inherently worse, I'm saying it's a fragmented and confusing user experience, in my humble opinion. My main dev machine still runs Manjaro because I've come to enjoy its opinionated handling of Arch, though if I were to re-image that computer I'd probably go back to either Fedora or Ubuntu.
> but I personally had much less headaches with it than I had with Ubuntu,fedora,debian, and CentOS.
Personally, I'm fine with using Ubuntu, Fedora, Debian, or even Arch. I'm not saying any one of them are bad or worse than the other. I'm just saying that, to me, Arch came with some additional challenges that I don't experience from other distros, mostly revolving around how software packages are found and installed.
I understand that a newcomer at the beginning can be confused about the relationship between pacman, pamac, AUR, yay, etc
similar cli programs exist in other distros though are not as encouraged.
That is how I read it, but it's all good. Sorry for misreading your tone.
> I understand that a newcomer at the beginning can be confused about the relationship between pacman, pamac, AUR, yay, etc
Perhaps that's the source of my confusion. So with:
Red Hat-like distros the tools are usually dnf or yum, which are evolutions over rpm.
Debian-like distros the tools are usually apt or apt-get (which are more or less the exact same thing), which are evolutions over dpkg.
With Arch, I kind of assumed that pamac and pacman are similar things, no idea if yay is related to anything else though. And I think pamac actually can install things from the AUR. My confusion definitely stems from loading up documentation from every different piece of software I tend to install, and each one of them listing a different utility for installing their package. If these are all the same thing with different UIs, installing packages from the same repositories, then that's definitely where I got lost.
And then I'd often be further annoyed to find out that the software vendor doesn't have a package for Arch, and nobody put one in the AUR yet, so I'd take the deb pkg and run it through debtap to get a PKGBUILD script. Doing which has netted me varied results.
AFAIK you can use any POSIX shell as `/bin/sh` on Arch Linux. By running `sudo ln -rsf /bin/dash /bin/sh`, dash works well.
I then moved to debian/ubuntu and recently switched my main server to Arch. And you are right - I got back this feeling of having all my 10 fingers in the system and living on the bleeding edge.
Now: this was probably not the brightest choice, as this server rund my docker containers and basically nothing more so it should have been Debian(a fire-and-forget OS)
Same!
Starting with a Stage 1 install was what got me (with some guidance of a friend and the perfect Gentoo Wiki) into Linux circa 2004 (IIRC).
Now, some 20 years later, i much prefer to have not to deal with something as... dare i say.. fragile... anymore.
Yes, much of the breakage i dealt with was probably self-inflicted but always a good learning experience - but most of the time not at the most convenient time :(
I did Stage 1's as well around the same time but eventually got tired of doing that every so often or fighting Portage and switched to Arch.
Then I got tired of dealing with Arch... and ended up on Fedora.
I always liked Gentoo and Arch, but I don't have the energy to put up maintaining them anymore.
Around 2004, I was building Gentoo up from stage1 just like many other commenters.
For 2024 and personal stuff I’m back on Debian and it’s safe enough I pull security updates daily - entirely automated and no review on my part. It essentially never causes a problem. Updating once a year sounds terrifying to me given the rate of vulnerability discoveries of late.
As ever your mileage may vary and your systems aren’t my systems, but Debian truly is a wonderful OSS project and as of August 2023 it celebrated its 30th anniversary!
Gentoo going binary feels weird :) I’ve still got a soft spot for Gentoo and what it enabled me to do 15 years ago when I had more time for personal hacks.
Now I'm in the process of moving my desktop computers to Archlinux, to enjoy better control and up-to-date software.
Servers I keep in Debian for the same reasons you mention: stability and safe automated updates.
I dunno, there's a fair amount to be said for having an up-to-date kernel, systemd, and Docker. :)
The main problem is that if I provide a specific repo for docker (to keep a fresh version) it can request some dependencies and bam! I have a Debian-Turend-Arch system to maintain :)
I tried Arch and what astounded me the most is that the docs didn't seem as good as Gentoo's. That surprised me because I end up looking at Arch's docs all the time and it's all of a very high quality.
But the Gentoo Handbook is really a masterpiece. I've never read a clearer explanation of how to go from unformatted disks to a working system.
I think that's a bit unfair. Everyone wants to support everything, but at the end of the day if you want to guarantee security and maintenance and do the job of a distribution you have limited resources on what you can look after. Something always has to give.
On any Linux distribution anyone can install what they want, but what you can genuinely claim to support is always limited by the amount of maintainers you have.
While I was untangling update dependencies one day I had it uninstall libc. There was a big warning advising me not to do that, but it was allowed.
Everything broke immediately, of course, but I recovered the system and the dependency problem really had been fixed, too!
This gave me a permanent positive impression of Gentoo. It's better to be allowed to do things than not.
Idr how this is handled on RPM-based distros, but on Debian it is part of the standard procedure for crossgrades.
(More impressive than this sort of flexibility, imo, is how NixOS and GuixSD sidestep this problem altogether.)
I'm going to install Solus OS / Solus Linux soon, had a good first impression with it's package manager, which claims to be reproducible but not like nix or guix are.
If you do systemd (which is what I'm using), then you might look at systemd.boot for UEFI. That's currently what I'm using.
I ask, because one issue I ran into was messing up the kernel config. Pulling the livecd config in and using that as the base config worked for me.
Took a day but now I'm on Solus and the package manager is reproducible because I can rollback a generation and rollback a rollback aka move forward a generation.
This is imprecise at best. There was a meeting where the release team concluded that most likely, there will be no _installer_ and _kernel_ support for 32-bit x86 at some unspecified point in the future. (At the current point in time, both are still delivered and fully supported.) In particular, you can still run multi-arch 32-bit/64-bit, allowing you to run 32-bit x86 software.
Which might mean people who want to run old proprietary 32-bit games/software are going to be annoyed, but that's not necessarily the distro/OS's problem; it could be argued that the user should install a 32-bit translation/emulation layer to run that stuff, ala DOSBox.
It's not really clear how long the Linux kernel itself will continue supporting such CPUs. The architecture certainly isn't something anyone really cares about (e.g. Meltdown wasn't patched for several months after it went public and 64-bit x86 got fixed).
That's not a good thing though, perhaps aggressively depreciating 32 bit will light a fire under their asses
If one were to rephrase it in today's language, Linux serve(d) to reduce e-waste.
So, yeah, it kind of is the distro's problem if they are moving away and against that mantra now.
Last I heard, even the last BlockBuster in the US is still using old PC's to run their DOS software. They harvest parts from old computers sold on e-bay. So, if you have any old computers laying around, they might be worth something these days.
Point of sale or industrial control computers are kind of just an offshoot of "embedded"; not something you need (or want) to run a browser or a modern GUI[0] on. You stick it in a cabinet or a kiosk and hopefully you don't have to think about it again.
[0] sadly also a browser
Outside of the enterprise crowd, Linux's next biggest audience are the tinkerers and hobbyists with too much free time and ancient hardware well past their Use By date. What a time it is that we can legitimately say it's better to run some version of Windows instead of Linux on them now.
> https://buildd.debian.org/status/package.php?p=base-files&su...
> https://cdimage.debian.org/cdimage/ports/snapshots/
Installer images for LoongArch are in the works as well.
We do that in Debian, too. FWIW, I am the one that eventually greenlit the removal of the ia64 port in the kernel because I was actually the one who took care of most of the issues in the ia64 port.
I also regularly debug and report (and sometimes fix) regressions in various upstream projects regarding targets such as 32-bit PowerPC. It's not enough to solely focus on downstream work, upstream work is as important if not even more important.
Is this referring only to ports (Portage) or does this mean enjoy compiling kernel and userland.
Is this even after disabling drivers and other code that is not needed for the x60.
I would argue that Debian has support for at least as many architectures as Gentoo:
> https://buildd.debian.org/status/package.php?p=base-files&su...
I know that because I am maintaining most of the obscure architectures in Debian with regular installation snapshots:
> https://cdimage.debian.org/cdimage/ports/snapshots/
Debian even has a Hurd port for both i386 and amd64.
The appeal of Gentoo is not compiling everything from source, it's having the freedom to install anything you want on nearly any hardware all with stellar documentation and minimal roadblocks. Want to run Enlightenment with OpenRC and NetworkManager on a laptop from 2008? Install Gentoo! Want ZFS as root on a smart refrigerator? Install Gentoo! Want a vanilla Gnome + SystemD install on a brand new laptop? Install Gentoo! The decision to ship binary packages only gives users *more* choices while other distributions have been actively removing one's freedom to choose. Debian, the so-called "universal operating system" just dropped 32-bit x86 support. You can install an alternative init system on Debian if you'd like, but it's a bit of a PITA. Meanwhile Gentoo allows you to pick between 17+ different stage 3 tarballs and 35 eselect profiles. Personally, I enjoy compiling everything from source and the flexibility that comes with it. On modern hardware it's painless. If you disagree, great! Go install a shiny new binary. The selling point of Gentoo has never been portage. It's always been the flexibility and the community.