Apps that haven't been ported to aarch64 (Store)

The move to aarch64 left the store with a big amount of apps that haven’t been ported to the new arch. While this is not a problem for people that use open repos -many open source apps were taken over and compiled to aarch64 by other people- the situation in the store is not nice.

So has jolla tried to contact devs or take other steps to improve this situation?. And what can be done?

Discuss.

9 Likes

This is what I feel I can do, (more coming hopefully)…

https://forum.sailfishos.org/t/aarch64-rpms-share/7265/12

I think the title should change to include abandoned apps in general. In the past there were some attempts to “foster” such apps with some success, e.g.

Most of these apps are open source ones and there are repositories in github. Also in OpenRepos there are many “forked” releases of apps. Is there any guideline how an abandoned app can be fostered, do we need some more documentation to encourage new developers?

ps saying all that, we do respect and appreciate the initial developers work for all apps.

Let the ping-fest begin.
@Venemo How about some IRC on aarch64?
That would be really nice :slight_smile:

3 Likes

How about some IRC on aarch64?

I don’t maintain the IRC client anymore, you will need to talk to @Thaodan for that.
In fact, I don’t even use Sailfish on my personal device anymore, and also switched to a Matrix client for my remaining IRC needs.

Also, what’s the big deal? AFAIK ARM64 devices can run old 32-bit code just fine.

1 Like

Do the noarch rpms builded by older SDK work on aarch64?

Yes, that would have been the expectation.
But this is SFOS…

If there is no architecture used inside (e.g. all python or shell) then my expectation would be: yes.

I just asked to be sure because I don’t have device with aarch64 SFOS.

If I understand things correctly, yes they should work.

No aarch64 builds situation affect Openrepos applications, too. There are several “AppNameHere (aarch64)” builds because the dev has left the scene and someone else had to just clicl the build button… Inevitable, but still makes the newestest device a lot less shiny :cry:

Can you please elaborate? I’m afraid I haven’t followed Sailfish’s aarch64 story.

1 Like

AFAIK, there are no major issues regarding native apps and aarch64. Your average app should just work after building for aarch64, if it doesn’t do anything too fancy.

Yes, sure.

Oh, I see. Looks like the problem is that they don’t support multilib.

Generally don’t install. I have a volla which is 64 bit and did run 32 bit arm fine with 3.4. As of 4.1, no more.

I’m pinging, using issues on github to contact people and offer to help. I’ll also push things to chum as I obtain permission. So far:

If anyone would like assistance getting into chum, I can help. It makes your life a lot easier and more or less can assure you of always having builds for current SFOS …
I’ll keep editing this list until I’m through.

  • just got feedback, it’s in the works

Candidates I’m culling from the old forum list, only including ones with github accounts:

  • no interest
  • communicating, it’s a bit of an odd structure to pull into obs.
  • requires an api refactoring?
  • frankly, too weird. forked anyway
  • not sure about irssi itself.

https://hub.darcs.net/dasimmet/Sailfish-Scanner

  • no longer maintained, will look at fork.

Telegram clients (we have fernschreiber…)

1 Like

I’ve pinged all of the above. Given some time, if they have GPL like lics, I’ll fork em and get them into chum. That I’ll split into topics when it’s time to test.

3 Likes