I would like to encourage all chum contributors to add at least one or two lines into the package description on OBS. 
4 Likes
Just updated mine 
I’d still recomend the people install from the Jolla store, though. That’s my priority in testing as I build. Chum will probably be my ‘bleeding edge’ (cough) code in future. That is to say, testing.
The solution was:
BuildRequires: pkgconfig(libjpeg)
BuildRequires: pkgconfig(libopenjp2)
BuildRequires: pkgconfig(libtiff-4)
BuildRequires: pkgconfig(freetype2)
BuildRequires: pkgconfig(libwebp)
BuildRequires: pkgconfig(libwebpdemux)
BuildRequires: pkgconfig(libwebpmux)
Iterative testing: just leave the ‘release’ tag empty and you can get obs to rebuild on simple changes to the .spec file (thanks rinigus!)
Or you could use chum:testing for the bleeding edge and push it to chum when it’s working acceptably?
1 Like
Of course, that’s what I meant.
There are also some subtle and not so subtle differences between just building in the sdk, tagging in github, uploading to harbour and ‘semi-automated’ builds. I’m not so sure yet.
I also have some more complicated projects which I’ve been ‘faking’ in a sense. For instance, Imageworks has included the PIL library. I’ve just pushed binary library depends (the cpython stuff) into an application library context. I should be building those. …
And if you got the Python stuff packed, I’m happy to have a look on it and hopefully get my python dependencies also packaged for my project here/here. Somehow I’m lost with that, so help is still welcome there!
Sure ting For the moment, I’m cheating by simply unpacking the wheel files and using / abusing :
equals(QT_ARCH, arm64): {
python.files = lib/arm64/*
DISTFILES += lib/arm64/PIL/* \
message("!!!architecture aa64 detected!!!");
}
python.path = "/usr/share/harbour-simplecrop/lib"
INSTALLS += python
The advantage to this approach is that I ‘KNOW’ that this library works with this version of SFOS and this version of the app. But it’s a lot of work to keep it up-to-date. And it’s not very secure if the library in question takes user/external input.
As a small milestone, there are now 100 packages available in chum:
12 Likes
I only had time to reconnect to the forums and only discovered chum in the community now, but…
Woah!
Finally something like F-Droid or like bioconda that some of us (including my self) were hoping for!
THAT! IS! AWESOME!!!
Thank you guys for starting this!
(Instantly switching as many of the package I was getting from openrepos as possible)
6 Likes
Cool project! I’ve submitted one of my applications, Audio Output Chooser, as well, to test it out!
2 Likes
which network and channel?
oftc, #sailfishos
1 Like
Submitted a couple packages that I find useful & hope others might find useful as well:
https://build.merproject.org/package/show/sailfishos:chum/fuse-sshfs
https://build.merproject.org/package/show/sailfishos:chum/tig
https://build.merproject.org/package/show/sailfishos:chum/wget
3 Likes
We (me and @piggz) are supposed to make a list of current apps available in Chum. Just got busy with other things and hoped that OpenRepos integration will kick off making that work redundant. As the integration is stalling, maybe should revisit the list generation in the near future.
4 Likes
Possibly silly question:
At what point does Chum become something that’s impacts the day-to-day experience of average Joe SFOS user?
Context - I did at one point over two years ago go through the shenanigans of getting Open Repos installed, but six months later some SFOS update broke compatibility, and in the two years since i haven’t noticed its absence. But… i [might] have noticed that absence if rectifying matters was a quick fix that immediately brought greater utility into my daily smartphone usage.
The idea sounds good but what I’m afraid of is fragmentation. We had the Jolla Store, then Openrepos, now this. I’ve noticed many users, including myself, are at least partly technical people so we could swallow it. However, regular owners would be extremely confused which is bad for the popularity of the platform. Could this new store perhaps supersede instead of complement Openrepos?
1 Like
A “good” idea would be to have Jolla allow for chum to be activated through the setting in the phone (Untrusted Software) and NOT allow for a gui so that you somehow know what you should do with the command line in order to install stuff.
But i doubt this would be popular with Jolla.
Fragmentation is a problem and the main cause of it is that Jolla hasn’t found a way to work with the community on the OS. Hence multiple “stores”, multiple solutions to functionality and other issues. And the result of that is an OS that is inferior to what it could have been.
2 Likes
I wonder if I am the only one who gets certificate expiration error while opening https://build.merproject.org/package/show/sailfishos:chum/wget and other urls at that site. This happens both in Desktop Firefox and Chromium. Viewing the certificate shows that expiration was at 30.8.2021.
2 Likes
Certificates have changed together with URLs. Use
https://repo.sailfishos.org/obs//sailfishos:/chum/4.1.0.24_armv7hl/noarch/
and similar
2 Likes