It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Darvond: Okay, that works for you. But not for erryone else. Not everyone wants to download 1.5 GB of devtools just to get OpenRCT2 running because Libduktape isn't included with my distro.
No argument from me. Only do this if it's your cup of tea.
Kubuntu then?
Probably.

Still a few months away till I buy a new PC.
avatar
ZFR: Like hummer said:
avatar
hummer010: I've been running the same install of Arch since 2012. It's on its third system now. I love not re-installing.
avatar
ZFR: But that 2012 Arch is very different from 2021 Arch. As different as say 2012 Ubuntu vs 2021 Ubuntu. Those small changes took place every new version.
No its not. This is the whole point of the rolling release. When a major change takes place, I get notified of it during a system update. It will go something like "Package A has been replaced with Package B. Would you like to remove Package A and Install Package B". I always say yes. For example, I'm running Mesa 21.0.2 and Kernel 5.11. It's as current as any other Arch install that's kept up to date.

Now, one of the common complaints about Arch is that those major changes often break things. I've been lucky, I guess. In the last 9 years, my system has been rendered non-booting twice. Both times it was related to the nVidia proprietary driver and kernel modules. Both times, it was easy to fix using a chroot from an Arch installer stick. My current system is all AMD, so I don't need proprietary drivers for graphics.
avatar
ZFR: Like hummer said:

But that 2012 Arch is very different from 2021 Arch. As different as say 2012 Ubuntu vs 2021 Ubuntu. Those small changes took place every new version.
avatar
hummer010: No its not. This is the whole point of the rolling release. When a major change takes place, I get notified of it during a system update. It will go something like "Package A has been replaced with Package B. Would you like to remove Package A and Install Package B". I always say yes. For example, I'm running Mesa 21.0.2 and Kernel 5.11. It's as current as any other Arch install that's kept up to date.
I get it, but that's my point. I'm not saying your OS is different from the uptodate current releases. I'm saying your OS is different from the one you had in 2012. At the very least, the version you had in 2012 would be using 3.4.x kernel and KDE plasma 4 (if you went with that DE). That's very different from the 2021 version. It's "continuous", but if a person looked at your OS in 2012, went into a coma, woke in 2021 and looked at your OS he'd be looking at two different OSs.

avatar
hummer010: For example, I'm running Mesa 21.0.2 and Kernel 5.11. It's as current as any other Arch install that's kept up to date.
So it is different. You couldn't have been using them in 2012. Your OS is different from what it was back then.

I'd rather keep exactly the same version of OS, even if it means not having an up to date version of many things (except security updates and the like), then after a few years just do a complete overhaul. So if I use a rolling release when a major change takes places I either say yes and change Package A to B (in which case I no longer have the lack-of-change that I want), or choose no, in which case I might as well use LTS.
Post edited April 16, 2021 by ZFR
avatar
Darvond: Right, but what you are proposing is the same sort of software staleness that gives developers headaches via bugs being reported against obsolete versions.
As an upstream software developer myself, I disagree with this. Well, of course I do not say there are never such issues, but my experience is the polar opposite of the xscreensaver maintainer one, so I would advise against making hasty generalizations based on their case only.

Having our software packaged in Debian repositories means that Debian users are not going to send us bug reports. They will send them to Debian bugs tracker instead, where the maintainer for our software can do some triage before forwarding to us only what is relevant.
EDIT: sorry wrong thread.
Post edited April 16, 2021 by ZFR
avatar
hummer010: No its not. This is the whole point of the rolling release. When a major change takes place, I get notified of it during a system update. It will go something like "Package A has been replaced with Package B. Would you like to remove Package A and Install Package B". I always say yes. For example, I'm running Mesa 21.0.2 and Kernel 5.11. It's as current as any other Arch install that's kept up to date.
avatar
ZFR: I get it, but that's my point. I'm not saying your OS is different from the uptodate current releases. I'm saying your OS is different from the one you had in 2012. At the very least, the version you had in 2012 would be using 3.4.x kernel and KDE plasma 4 (if you went with that DE). That's very different from the 2021 version. It's "continuous", but if a person looked at your OS in 2012, went into a coma, woke in 2021 and looked at your OS he'd be looking at two different OSs.

avatar
hummer010: For example, I'm running Mesa 21.0.2 and Kernel 5.11. It's as current as any other Arch install that's kept up to date.
avatar
ZFR: So it is different. You couldn't have been using them in 2012. Your OS is different from what it was back then.

I'd rather keep exactly the same version of OS, the same immature college-John, even if it means not having an up to date version of many things (except security updates and the like), then after a few years just do a complete overhaul. So if I use a rolling release when a major change takes places I either say yes and change Package A to B (in which case I no longer have the lack-of-change that I want), or choose no, in which case I might as well use LTS.
Sorry, I misunderstood you. I thought you were saying that a fresh install in 2021 would be different than my current install from 2012.

You are absolutely correct, it is drastically different than it was in 2012. I would be surprised if there is a single package that has been updated.

This just reiterates that we're looking for different things. You'd like to keep the same version of the OS. I don't want to have to go through an upgrade or reinstall process. That's the beauty of Linux - there's an option for everyone.