Update Snap version

[Kyuyrii]

I noticed that the Snap version is outdated, over three years old.

I created this simple snapcraft.yaml to generate an updated Snap version.

Since I don't understand MuseScore, I don't know the right way to test it, but I managed to generate the Snap, install it, and open it normally.

[rettinghaus]

Looks like this could address #15994.
Do you think it would be possible to build a deploy action with https://github.com/marketplace/actions/snapcraft-action?

[cbjeukendrup]

There are a few things to sort out before we can merge this:

• By allowing this file in our repository, we are essentially taking on the burden of maintaining and supporting the snap package forever, while nobody of us currently has experience with this technology. We would be expected to provide the same level of quality assurance, but Mac+Win+AppImage is already more than enough platforms for the manpower that we have. We would be expected to help users with troubleshooting issues, but we have no knowledge about this ourselves. So how should that work?
• Is it usual to keep such a file inside this repo, and shouldn't it be in a separate repo? I'm wondering about that because the file contains a link to the repo, rather than just using the checked-out version of the repo. So you'd clone the repo to get the snap file, and then the snap building process will clone the repo again?

[rettinghaus]

@cbjeukendrup The answer to your second question is yes, it belongs in this repo, see https://snapcraft.io/build.

[Kyuyrii]

There's a version of MuseScore on Snapcraft, which is why I mentioned updating it. The publisher is verified, and I assumed one of the developers is the publisher.

The snapcraft.yaml file can be inside or outside the main repository. You can create a repository just for the Snap version if you want.

In this case, this snapcraft.yaml file uses the latest officially released version (4.6.0), rather than the current repository version. If you want to build it, you only need the snapcraft.yaml file; the rest will be downloaded during the build.

You can also generate the Snap on the Snapcraft website instead of locally.

[cbjeukendrup]

The verification was done by the previous owners of MuseScore, and nobody of the current team has access to the account with which that was done (see #15994). So that's another hurdle, but hopefully someone from the snapcraft team is willing to help with that (or maybe we can contact the previous owners, and they still have the keys somewhere).

[pachulo]

Original MuseScore snap maintainer here.
As I explained here, I don't have the time anymore to maintain this; I'm not even an user of MuseScore anymore.

So that's another hurdle, but hopefully someone from the snapcraft team is willing to help with that (or maybe we can contact the previous owners, and they still have the keys somewhere).

If you are interested, I can invite you so that you can manage it, as I still have access to the MuseScore name on snapcraft.

Anyway, @Kyuyrii can you try to open a PR on the repo I was using to create the builds of the snap?
We can see it it builds OK on launchapd, upload it to the beta channel, and ask the community for some testing.

[Kyuyrii]

Anyway, @Kyuyrii can you try to open a PR on the repo I was using to create the builds of the snap? We can see it it builds OK on launchapd, upload it to the beta channel, and ask the community for some testing.

I opened the pull request with the updated snapcraft.yaml.

pachulo/musescore-snap#8