Download page for AppImage release packages with installation instructions
For the final release packages, we will have nice urls to put on all the download pages:
* musescore.org/download/musescore-32.AppImage
* musescore.org/download/musescore-64.AppImage
These will directly fetch the package from bintray and push the download. In the meantime, on the download page on musescore.org we can show them the installation instructions.
It can be a mix of some text (as little as possible) and images, laying out the different steps to take. Self-explanatory images will be helpful across languages.
Comments
great!
Will need to communicate to the truely uninitated Linux user that you have to manually set the permissions on the downloaded file to be "executable" before executing it (if user doesn't want to "install" it...)
Looks good! @ericfont is working on ARM packages too, they will be 32 bit only for the foreseeable future, but no doubt 64 bit will arrive in due course. Users can find the one they need from the Terminal:
Output will be:
Here are some images of the steps to give execute permission. I'm hoping to find time to make a little YouTube video showing the process in full, and to update the installation instructions in the handbook.
I agree with shoogle to use the standard cpu terminology: i686, x86-64, armv6, armv7, armv8. I'm almost done with setting up arm builds on travis. But since the steps I'm using are pretty much transferrable between armv6, armv7, & armv8, then I'm probably going to ahead and make the automatic armv8 builds (FYI, I setup an x86-64 debian docker image to run in travis that has the arm versions of all musescore dependencies and a cross-compiler toolchain installed here: https://hub.docker.com/r/ericfont/musescore/builds/bvvjzktuhwm2fry7m4oc… ...as you can see from the docker file it is straightforward to add armv8 to that).
@Thomas. May I split the handbook installation instructions onto separate pages for Windows, Mac and Linux? This is done for the compilation instructions in the Developers' Handbook, and I think it makes things a lot clearer. It means that users only see the information relevant to them, and it would allow room for a more detailed explanation of the difference between different builds for each system (Windows MSI vs Portable, Linux Distribution Packages vs AppImages) without cluttering the main page.
As soon as we have a page explaining how to handle the AppImage, we can link to it in the bintray version description. See #102126: AppImage nightlies on bintray: set version description with installation procedure
Thanks for the heads up on naming convention. I will change it.
As for the installation instructions, we could actually work them into the handbook at https://musescore.org/en/handbook/installation-0#linux
This way they can also be translated.
@shoogle I'm thinking how to split up the installation page in the least painful way, so the translations can be preserved somehow and also that the result is nicely packaged in the handbook PDF. I'll report when I have the solution.
For English it's as simple as making the three new pages, clicking "edit" on the original page, and copying the relevant bits of the Markdown code to the new pages. I'd have thought it would be the same for the translations, but perhaps they work differently to the English page. It should be obvious what we've done though so the translators could update their pages without too much difficulty. We could create the new pages but not delete the text on the original English page while we wait for the new pages to be translated.
I gave it some thought, and I couldn't find anything else but to add html comments inline explaining the translators what to do. So, I'll give it a go.
Cool. Let me know when you've created the Linux page. If you just want to copy the existing information across then I'm happy filling in the details about AppImages.
@shoogle ok, the split is ready: https://musescore.org/en/handbook/installation-0 > Linux
Thanks Thomas. I added basic instructions for AppImages and will add screenshots and improve them as time goes on. Others are welcome to edit too obviously.
So 2.0.3 is out and the download links for the AppImage(s) are
* https://musescore.org/en/download/musescore-i686.AppImage
* musescore.org/en/download/musescore-x68_64.AppImage https://musescore.org/en/download/musescore-x86_64.AppImage
* https://musescore.org/en/download/musescore-armhf.AppImage
If these are ok, we need to put them somewhere up on the Download page https://musescore.org/en/download
Feel free to make a proposal. Once settled, we can mark the download page translation as outdated so the translators can update the localised versions.
I would say right under the linux penguin have links "x86 32-bit any Linux" and "x86 64-bit any linux". And then maybe have a first subheading under the "Linux" heading be "AppImage" with a quick description, and the links again.
Be aware, I don't think shoogle or I ever got jack to work with the AppImages. Also, on ARM if run plugin that opens up new window, will crash.
Thanks for listing up the open issues Eric. I have been following the progress from a distance, so it's handy to get this summary. I assume the plugin issue has a higher priority than Jack, but tell me otherwise if not. In any case, I'll make sure these issues are communicated.
Thanks Thomas! Shoichi already got in there and updated the version on the Downloads page so I just added the AppImage links straight to the page.
The crash on ARM AppImage when executing a plugin that opens up a window is due to the lack of the library "libQt5EglDeviceIntegration.so.5" which is simply missing in stable Debian "Jessie" (which is what I built the ARM AppImage on), although it is present in the unstable Debian "Sid" (https://packages.debian.org/sid/armhf/libqt5gui5/filelist). But fixing that probably involves upgrading a bunch of Qt libs in the docker image, so I though to table that issue and wait until MuseScore upgrades to Qt 5.6 to resolve that.
@Thomas, I just noticed your 64-bit link is wrong. It should be x86_64, not x68_64. The version on the downloads page is correct (and so doesn't work right now).
@shoogle Thanks, fixed link deployed.
The page http://prereleases.musescore.org/linux/nightly/ is now redirected to bintray.
Next is to make sure the AppImage info is listed on all the localised versions of /download
I made a video explaining how to install the AppImage: https://www.youtube.com/watch?v=btmK0Cg1DJs
I believe this is now done. We have a video https://www.youtube.com/watch?v=btmK0Cg1DJs and the download page https://musescore.org/en/download links to https://musescore.org/en/handbook/install-linux#AppImage-download
Automatically closed -- issue fixed for 2 weeks with no activity.