Tag (and APK) for latest version is missing #4
Comments
|
Hi
I think there's a bunch of web sites that allow to download specific apk
versions, for example:
https://apkpure.com/ktodo/com.kos.ktodo
…On Thu, Jan 10, 2019 at 11:49 AM Izzy ***@***.***> wrote:
According to Playstore, there's a v2.2 – but the releases page has only
v2.1. Could you please fill the gap? Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAoWasRvorontw6-Z6LdoC0Pas5lu-4eks5vB28XgaJpZM4Z55Zx>
.
|
|
@eprst that might well be. But instead of sending users hunting, wouldn't it be favorable to provide it first-hand? You did so before 😉 Apart from that, the updater for my repo (where your app is available as well using the F-Droid client) cannot deal with "a bunch of web sites that allow to download specific apk", just with Github and GitLab 😇 |
|
Hi
OK, I'm sorry that I didn't provide the apk when it was just released.
Pulled 2.2 apk from the play store and created a release on github. Looks
good now?
…On Thu, Jan 10, 2019 at 3:14 PM Izzy ***@***.***> wrote:
@eprst <https://github.com/eprst> that might well be. But instead of
sending users hunting, wouldn't it be favorable to provide it first-hand?
You did so before 😉
Apart from that, the updater for my repo (where your app is available
<https://apt.izzysoft.de/fdroid/index/apk/com.kos.ktodo> as well using
the F-Droid client) cannot deal with "a bunch of web sites that allow to
download specific apk", just with Github and GitLab 😇
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAoWau-NA-N8-1sG2NwQ5ZcnGUWu7Nrhks5vB58VgaJpZM4Z55Zx>
.
|
|
Thanks, yes! Update should appear in my repo with the next sync tomorrow. PS: Looks like your app would also fit the inclusion criteria of the official F-Droid repo. If you would like to see it there, let me know and I gladly assist you (disclosure: I'm one of the maintainers there). |
|
Great
Honestly I don't care that much, but we can put it in F-Droid if that's not
too much effort on my side (sorry, quite busy with other stuff these days).
Also, who will be responsible for pushing updates there?
thanks
…On Thu, Jan 10, 2019 at 4:55 PM Izzy ***@***.***> wrote:
Thanks, yes! Update should appear in my repo with the next sync tomorrow.
PS: Looks like your app would also fit the inclusion criteria of the official
F-Droid repo <https://f-droid.org/>. If you would like to see it there,
let me know and I gladly assist you (disclosure: I'm one of the maintainers
there).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAoWav0gnoBExm7m5jmW9Q6lCUPEiE51ks5vB7a3gaJpZM4Z55Zx>
.
|
|
As long as you tag each new release (and increase versionName/versionCode accordingly), and don't add any "proprietary stuff" or non-whitelisted Maven repos, our team will take care to build updates and publish them (disclosure: I'm one of the F-Droid maintainers). Still, should complications arise, we might need your help to solve them. Does that sound good for you? Then I'd go ahead and "trigger the process". |
|
Fine by me.
But why do you care about mvn repos? Your updates will be based on released
.apk's as I understand it, or are you actually building from source?
|
|
Apps in my repo are based on the APKs, true. Apps in the "official repo" are solely relying on the source code (no binaries accepted), and are built from that. As for "external sources" like MVN repos: only some whitelisted Maven repos are permitted (there's trust involved; I'm not a dev, so I cannot explain that in detail – as far as I understood, some ship the signed source along and some don't, so the former can be "trusted more" while with the latter you cannot tell what source they've built from). So in short: For my repo, the APK is sufficient. To go for the official repo, the APK is irrelevant but the source is important. |
|
@eprst another point that needs clarification for the official repo to accept your app (and would be good to add regardless of that): What license is this project using? |
|
@eprst a year later: any decision on the license yet? |
|
Errm… And again, tags (as well as APKs) are missing. Last version on Play was 2.3 before you unlisted. So any chance here? |
|
With the latest commit being more than 2 years ago it seems you've abandoned this app – its disappearance from PlayStore seems to confirm this. Further, the last release here is v2.2 – while the last one I've seen on Play was v2.4.3, which suggests it went close-source in between. As hope dies last, I make one more try to get an answer – or two now: Is the app still maintained, if so under what license (back in 2012 you've said WTFPL, but it's still not pointed out in the Readme or anywhere else), and where to find the updates? Oops, that were 3 questions, but I hope you don't mind… |
According to Playstore, there's a v2.2 – but the releases page has only v2.1. Could you please fill the gap? Thanks!
The text was updated successfully, but these errors were encountered: