# MuseScore-2.1-x86\_64.AppImage on MiyoLinux i3 Jessie 64bit

**URL:** <https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279>\
**Category:** Using AppImages\
**Created:** [January 11, 2018, 8:01am UTC](https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279 "2018-01-11T08:01:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![globetrotterdk](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/globetrotterdk/32/102_2.png) [@globetrotterdk](https://discourse.appimage.org/u/globetrotterdk)\
**Post date:** [January 11, 2018, 8:01am UTC](https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279/1 "2018-01-11T08:01:53Z")

</div>

I love the AppImage format, but have run into an irritating problem. I would like to run the MuseScore 2.1 AppImage on MiyoLinux, which is a Devuan based, minimal distro. MuseScore refuses to run, but will install. It turns out that this is due to a lot of unmet dependencies. My question is if there isn’t some way that (for example) a `$ sudo ./MuseScore-2.1-x86_64.AppImage install` command (for all users) could be created to pull in all needed dependencies? I realize that there is a security issue here, so the question is how it could be implemented. While in reality there are no issues with the MuseScore AppImage, it is a real pain in the butt to have to research each cryptic message that it kicks up, to find the necessary file to install. This can get boring extremely quickly with a lot of depends.

---

<div class="post-metadata">

**Author:** ![globetrotterdk](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/globetrotterdk/32/102_2.png) [@globetrotterdk](https://discourse.appimage.org/u/globetrotterdk)\
**Post date:** [January 11, 2018, 8:07am UTC](https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279/2 "2018-01-11T08:07:54Z")

</div>

BTW, I would like to point out that one of the advantages of the AppImage format, as I see it, is for those of us that prefer to at least remain systemd agnostic. AFAIK other formats like Flatpak and Snaps would just automatically pull in systemd as a dependency.

---

<div class="post-metadata">

**Author:** ![probono](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/probono/32/81_2.png) [@probono](https://discourse.appimage.org/u/probono)\
**Post date:** [January 13, 2018, 10:46pm UTC](https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279/3 "2018-01-13T22:46:06Z")

</div>

> [@globetrotterdk](#):
>
> My question is if there isn’t some way that (for example) a $ sudo ./MuseScore-2.1-x86\_64.AppImage install command (for all users) could be created to pull in all needed dependencies?

No, there is no such feature and it is not planned.

> [@globetrotterdk](#):
>
> MiyoLinux, which is a Devuan based, minimal distro.

This is not one of the supported distributions. Please try a “mainstream” desktop distribution such as Ubuntu, Fedora, openSUSE, etc.

---

<div class="post-metadata">

**Author:** ![probono](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/probono/32/81_2.png) [@probono](https://discourse.appimage.org/u/probono)\
**Post date:** [January 13, 2018, 10:46pm UTC](https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279/4 "2018-01-13T22:46:51Z")

</div>

> [@globetrotterdk](#):
>
> BTW, I would like to point out that one of the advantages of the AppImage format, as I see it, is for those of us that prefer to at least remain systemd agnostic.

Yes, AppImages do not require `systemd`.

---

<div class="post-metadata">

**Author:** ![globetrotterdk](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/globetrotterdk/32/102_2.png) [@globetrotterdk](https://discourse.appimage.org/u/globetrotterdk)\
**Post date:** [January 14, 2018, 8:00am UTC](https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279/5 "2018-01-14T08:00:04Z")

</div>

All of the distros listed use systemd. So systemd is “mainstream”? Anyway, another way of looking at it is that AppImage only supports certain WMs or DEs, as there are non-systemd linux distributions that work fine with AppImage as long as it isn’t a version with a “minimalist” WM, lacking most of the necessary dependencies.

I personally think that this will prove to be a mistake, but we can agree to disagree.

[Defying systemd - or how to do wrong things the right way [en] - Klaus Knopper](https://youtu.be/lDXsw2ijRkw)

---

<div class="post-metadata">

**Author:** ![probono](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/probono/32/81_2.png) [@probono](https://discourse.appimage.org/u/probono)\
**Post date:** [January 17, 2018, 7:44pm UTC](https://discourse.appimage.org/t/musescore-2-1-x86-64-appimage-on-miyolinux-i3-jessie-64bit/279/6 "2018-01-17T19:44:06Z")

</div>

If the largest distributions with the most users such as Ubuntu, Fedora, openSUSE, Debian etc. use systemd, then yes, I guess we can consider systemd “mainstream”.

No AppImageKit components require systemd though, at the moment.

AppImages _may_ run on more niche systems, especially if they come with the usual libraries as part of their base system, but we don’t make any such guarantees. Here is a list of what we assume to be present in every target system:

> <https://github.com/AppImage/AppImages/blob/master/excludelist>
