Hi there!
Is the audirvana-studio RPM package distributed via standard RPM repositories?
I ask because Bazzite uses standard RPM repos for package installation and distribution, but it’s not updating v3.0.1 to the newest (v3.0.2) package.
Never mind. I found the answer online that locally installed RPM packages do not update via the normal layered RPM package updates.
RTFM for me.
1 Like
Just to follow up…
It was surprising how easy it was to uninstall the previous version and install the new version on an immutable OS like Bazzite. Really liking the Linux world right now.
1 Like
It’s interesting to me that people like the immutable aspect (though if you read the Bazzite docs, they resist the label). I’ve experienced dependency versioning aggravation, so I understand the desire to avoid that. My personal approach to Linux is from the other direction - I love the fact I can change just about anything I want to if I’m able to learn how.
1 Like
I may get there, but I wanted to start with something that comes wrapped up with some entertainment (Steam games, streaming, etc.) and is difficult to bork. Once (or if) I get used to the Linux methodologies, I may move to something I can build from the ground up, or at least something that’s not as restricted. We’ll see.
1 Like
Ah, OK. I’m old enough that I pretty much missed the whole gaming thing. (I know, it’s a gap in my education. 
) Makes sense. Unless there’s something specific you really want to do that Bazzite doesn’t allow, no reason to change.
I mostly play more casual games for relaxing (not a hardcore gamer), and I just turned 60 this year. Never too old to game to some extent, IMHO.
1 Like
With Mint I get the Audirvāna updates as well. I don’t have to get the new version manually.
I must be getting old , is there a version of this in English 
2 Likes
How familiar with Linux are you, so any explanation doesn’t waste time with stuff you already know?
Yep, the advantage of have native .deb / .rpm package installation support on your distro. 
1 Like
Absolutely nothing , I’ve been Windows and MS , I am even a MS certified developer so I never ventured into Linux
I was joking , I read the thread and it didn’t mean anything to me !
1 Like
I pretty well figured, since I gave it a laughing emoji. But it’s pretty simple, so I’ll give an explanation anyway.
Linux, like Windows or MacOS has different versions. Instead of coming from one company, like Windows or MacOS, Linux versions come from various developers all over the world. These versions are called distributions, or “distros” for short.
While all the distributions have some version of the Linux kernel (the core of the operating system), different distros come with all sorts of different applications. For easy installation and removal, these applications are commonly organized into “packages.” The various distros make managing the packages convenient by means of, heh, yes, package managers.
The most often used applications for a distro are assembled in “repositories.” When you tell the package manager to do a system update, it updates all the packages on your system for which there are new versions in the repositories.
But what if an application you want, like Audirvāna, doesn’t sit in one of the repositories? Then you can use the package manager to install a particular package/application “locally.” It won’t be updated in the general system updates. You have to take care of updating, or removing the old version and installing the new one, separately. That’s what Glen did with the Audirvāna application on his distro.
Now what about “immutable”? Traditionally with Linux distros, you can change anything and everything if you like. No confidential bits, unlike Windows and MacOS. But this can create problems. Whether for Windows, MacOS, or Linux, applications expect certain versions of things like libraries or databases to be present in the operating system on which they’re installed. Since Linux is so decentralized, it can sometimes happen that application A expects version 1.0 of a library, while application B expects version 1.5. Either A or B or both won’t work in that situation. So developers can get busy with questions from users whose applications don’t work. Or (when you have the freedom to change anything) there are multiple other ways to screw up. So the developers of the distro Glen uses have decided to lock down some parts of the system so users can’t monkey around with them. Those bits are unchangeable, “immutable.”
And that’s all, folks!
2 Likes
Thanks a clear explanation .
I prefer Windows as I don’t have to worry about it, writing code is hard enough without worrying about a moving OS platform . You just need to keep up with .NET versions
Thankfully I am retired and no longer code except for fun !!
1 Like
Since it’s Linux, there’s something for everyone. For people who don’t want to deal with a lot of change, there are long term support versions of many popular distros. Ubuntu LTS has 5 years of support as standard, extendable to 10 or even 12 years. These distros concentrate on stability, and development for them can be correspondingly paced.
There’s something analogous in the Windows world - I get the Insider fast track developer builds, which update every 2 weeks or so, while the public non-developer versions run at a much slower pace.
1 Like
I first tried Linux about 10 or 12 years ago with Kubuntu (Ubuntu w/ KDE), and it was OK, but not nearly as polished as the distros are today. I’ve looked at a bunch of them in containers this past week, and there absolutely is something for everyone. And, it’s just getting better at a rapid pace.
2 Likes