First, Everybody just chill a bit here.
Lets make some things a bit more clear and laid out since there is some confusion. Especially around the term "support".
Potential for installation and usability does not equal "support". Linux Distros do not "support" applications just because it can be installed in some way shape or form.
Linux Distros support applications by creating and "maintaining" a package of the application from start to finish (dependency resolution, testing, troubleshooting, and updating). A "Package Maintainer" they are about as close to official "support" as you'll get (besides the actual application developer) because they volunteer to take responsibility of the said application package for the Distro. Users and in our case Qualified Guides also help "support" by testing and troubleshooting.
Now to the Facts:
BeeBEEP provides (supports) several Linux installs:
- Ubuntu 18.04 via a .deb,
- Snaps (via an
unofficial snap)
- "portable" packages via a tarball
There are only 10 packaged versions of BeeBEEP in repositories, looks like maybe 5 total actual Distros "supporting" BeeBEEP.
https://repology.org/project/beebeep/versions
The link above shows
"created" packages for repositories, these may or may not be officially supported and they may not be maintained current.
Packaged versions does not specifically entail that something is really "supported" or not, or if it can actually be installed or not.
For example: Chocolatey, winget, freshcode aren't Distros.
Note the fact that Debian is NOT on that list at the link, therefore Debian does NOT maintain (support) a package of BeeBEEP at this time.
The Snap can be (should) run on MX Linux as MX
does "support" Snaps, but as already stated, you have too boot using systemd.
There is no technical or ideological mumbo jumbo about any of that, its just a fact.
The linked page to the Snap install statistics
has nothing to do with Distros "supporting" BeeBEEP or not.
This page simply lists the Distros "used by" users who have it installed via Snap. NOT Distros supporting BeeBEEP via Snap.
Again, go back to the Repology link to see which distros created (possibly maintain (support) current) packages in their repos.
JayM is right, we don't "support" (yet) BeeBEEP directly. That doesn't mean you can't install it and we won't help you with it though.
And that doesn't mean we can't maintain (support) a package of BeeBEEP in the future.
Now to the good stuff:
directly at
@Michael_Logies
The process to get "support" for an application "in MX" is a Package Request as Jay stated,
but do not worry about doing one, I'm acknowledging the request right now.
JayM said the Portable package works and it seems some hacky workarounds will allow the .deb package to work.
Honestly I would use the Portable package as it comes from (supported?) by the actual developer. Trying to cram a cube through a circle hole with the .deb is not going to work well long term. And you should NOT be enabling repos to do such cramming unless you know exactly what you are doing. See JayM's or my signature blocks about breaking stuffs.
With all that out of the way, like I said your request to get BeeBEEP packaged and easily installable in MX Linux is acknowledged.
Its going to be awhile (few weeks) before I can give you a status update, unless someone else decides to tackle it. But again in the meantime I would
try the Portable package, if it works then use that, if not then post back here for assistance on that.
@Moltke appreciate you're help with this, really. But please do not state that MX "supports" an application just because it can be installed one way or another. "Installs and works under/with" and "Supports" are two different things. Neither MX nor Debian directly "support" BeeBEEP.
It can confuse new users. Also, pretty sure JayM tried the .deb, but told the OP to attempt to use the Portable version (which he did also test) because of the fact that it can help limit breakage from randomly trying things like the OP has now done by enabling (unknown said) repos.
Edited for Distros "used by" users
