I like this app! Will you publish it on Chum too?
Not in the short term, because I have not the faintest idea how Chum works 
Super easy.
Just request an account from @Keto
Create a package and a service file with 5 or 6 lines, point to your github and a tagged version, save, get it build….
2 Likes
Is the source code available anywhere?
You can download both the sources and the RPMs from the page linked in the initial post.
These should be always up to date, as that is where the build system automatically saves them after a successful build.
2 Likes
Whenever I read something is “Super easy” it tends never to be super easy
It starts with the fact that I don’t use GitHub (it’s owned by Microsoft), and I suspect there may be many other things in my workflow that are incompatible with Chum.
My other apps are only on Chum because @poetaster was kind enough to put them there.
2 Likes
As I have permission to use the github sailfishos-chum repositories, I could make the source available there.
I had gone the route of making the projects, like
conform to ‘dummy can build with sdk’ norms.
I can get the ball rolling, but probably won’t have time to maintain it.
2 Likes
That’s one of the reasons I wasn’t so keen on offloading this to you again, knowing how much you already have on your plate.
So no way to contribute using git or something? And it seems no license as well so it’s not open source?
Edit: Found a license in the src dir, is it safe to assume that it applies to the whole source, not only the dir? Cause it kinda implies it only applies to src.
If I get the project in the chum repos, then @nephros is already in a position to directly work with it so it’s not so unreasonable … @nephros, good idea?
1 Like
I had used MIT for musicex and multimodal after some discussion with @cypherpunks Originally, I wanted to use the anarchy in the UK unlicense.
2 Likes
I just to a look and it’s in go for the daemon (python for the qml part). Perhaps one of your projects might serve as a template? I still haven’t done a go project. … EDIT, I was looking at spliit but believe that’s in two parts?
I’ve accidentally dropped a LICENSE file (GPL) into the src/ directory at some point, it should not have disappeared by itself. 
1 Like
Cool. I’m one of those crusty gpl farts.
I have a question. Would it make sense to have this in two repos. one for the daemon, one for the app? The example I have in mind is:
GitHub - RikudouSage/SpliitApi: An unofficial Golang api for Spliit · GitHub (using nix in the build)
GitHub - RikudouSage/harbour-spliit: Spliit client for SailfishOS · GitHub
1 Like
Yes, the idea was that the daemon should be able to run on both Sailfish and a Raspberry Pi, so Go producing a self-contained binary with few external dependencies seemed like a good choice.
1 Like
Yes, Spliit is in two parts.
- api: GitHub - RikudouSage/SpliitApi: An unofficial Golang api for Spliit · GitHub
- ui: GitHub - RikudouSage/harbour-spliit: Spliit client for SailfishOS · GitHub
But there’s no auto build for the Go part if that’s what you’re looking for.
Heh. We hit reply at the same time with the same content.
Ok, but it’s a good idea to structure this way, or?
It was more of a coin toss between GPL and MIT and the former won this time
1 Like
I don’t mean to be disrespectful, but I think that for small projects like this, setting up this entire framework may be more trouble than it’s worth, as it’s unlikely that anyone will contribute anything particularly meaningful anyway.
It’s a messy rewrite of an even messier piece of software that’s over a decade old and is probably only useful to me.
I only put it on OpenRepos initially because it made it easier to install on my other phone without having to copy it over.