[please delete]

[havran]

---

[pekbro]

You should be able to make them run anywhere, so long as they are written
for linux, thats one if the good things
about linux.

If you want a nice rpm package or something,
thats the only reason to use a targeted distro.
Dependancies these days are nothing, we used to have to build stuff from source, practically everytime.

[havran]

---

[Greenstorm33]

Linux as a whole is a massive moving target so I think it makes sense to narrow your focus to something that's popular, provides a (relatively for Linux) consistent, well-defined environment, and is conservative rather than bleeding edge. Ideally you'd have something self-contained that you just install with a script, but I don't blame anyone who doesn't go that route. It's a matter of how big your userbase is, and, given that, how many support tickets you're willing to field for wider-ranging Linux support.

[audiojunkie]

Sure, it's understandable -- that might cover a large subset of Linux users who are interested in such products.

And then come the other requirements: such as using a particular version of Ubuntu -- and oh! only Wayland is supported.

OK, sure. Fewer variables to consider during a beta phase.

And then of course, after one reluctantly agrees to use a current Ubuntu-based distro in order to make good use of the .deb installers of some commercial apps instead of the sandboxed Flatpak versions (if even available and up-to-date), there is some damn dependency error. WTAH?!!!

And aside from all that it feels very restrictive and as if some (not all) commercial developers have agreed to steer their Linux customers into using Ubuntu (and maybe just some subset of its official flavors) -- but with unsatisfactory results.

Therefore, these days I'm starting to favor Linux DAWs that either have packages in whatever distro's main repos, or just provide a tgz to untar and an install.sh to run, and it just works -- on any distro.

There are ways to get around of the problems that people have mentioned in posts above mine. Here's what you need to do....

1. Without worrying about how your Linux DAW is packaged, pick the distro that you want to use.
2. Install Distrobox.
3. Create a Ubuntu Distrobox.
4. Install all of your DAW software onto that Ubuntu Container in Distrobox--including WINE, yabridge, etc.
5. Export your launchers to your distro of choice.
6. Use your Linux DAW in an environment that you actually enjoy.

Distrobox is seamless. It integrates completely into your distro of choice, so that you won't even have to think about what distro it is really running. Everything--and I really do mean EVERYTHING that you want to use in Linux natively will be available to you.

Oh, here's the link: https://distrobox.it/

Watch some youtube videos about it. Get a gist of what it does. It will change your Linux experience for the better.

EDIT: While I'm at it, I ought to mention that with modern tools such as Distrobox, Toolbx, Flatpak, Appimage, and even Snaps, there should be very little risk ever again on Linux of ever experiencing Dependency Hell. Install as little as you can directly to your chosen distro of choice, and instead use the sandboxed options that I just mentioned. Goodbye Dependency Hell.

[havran]

@audiojunkie -- Thank you for your helpful and informative post.

[audiojunkie]

One thing that I want to clear up that I think you are misunderstanding: These days, dependencies are almost always backwards compatible. That means it is always best to use the newest version of your distro, and plugins and apps compiled from orevious versions will almost always just work. To use your example: Ubuntu 24.04 should have no problem at all with using plugins compiled for 18.04 LTS.

Also, There are now enough plugins and software that you nay not need to use Windows software. I don’t currently use any Windows software, and I’m doing fine.

[havran]

---

[havran]

(why bother)

[audiojunkie]

One thing that I want to clear up that I think you are misunderstanding: These days, dependencies are almost always backwards compatible. That means it is always best to use the newest version of your distro, and plugins and apps compiled from orevious versions will almost always just work. To use your example: Ubuntu 24.04 should have no problem at all with using plugins compiled for 18.04 LTS.

Except when they don't, e.g., Tracktion's Waveform 13.

A gelatinous house of mirrors with goldfish would be more fun than your attempt to clear up what you think I might be misunderstanding.

Tracktion doesn’t have the greatest reputation for being stable and bug free—regardless of the OS it is being developed for. That’s not a very good example.

[havran]

---

[audiojunkie]

Dude. You’re drunk. Go home.

[dexrow]

I am a big supporter of running several versions of some software csound, python, waveform like you mentioned so that you don't loose features.... It may be that certain versions of linux just won't or don't do that.

[jonljacobi]

One thing that I want to clear up that I think you are misunderstanding: These days, dependencies are almost always backwards compatible. That means it is always best to use the newest version of your distro, and plugins and apps compiled from orevious versions will almost always just work. To use your example: Ubuntu 24.04 should have no problem at all with using plugins compiled for 18.04 LTS.

Except when they don't, e.g., Tracktion's Waveform 13.

A gelatinous house of mirrors with goldfish would be more fun than your attempt to clear up what you think I might be misunderstanding.

Tracktion doesn’t have the greatest reputation for being stable and bug free—regardless of the OS it is being developed for. That’s not a very good example.

Yes, it was a super crash fest for a while, but my latest experiences have been much, much better. macOS. I can't speak to Linux.

[havran]

---