New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release it on Fdroid #4
Comments
@marc0x1 thanks but no plan yet. it is already on izzyondroid |
Thanks anyway! Keep in mind that izzyondroid is kinda "unofficial" and the fdroid main repo is more popular PS: Your app is fantastic |
@marc0x1 you are right and to be honest I have 2 issues with fdroid even though I LOVE thé concept:
and thank you for the kind words! makes want to do more open source ;) |
Yeah getting reproducible builds on the F-Droid repo might be challenging. There needs to be an easier way for users to learn about other F-Droid repos and access them. |
perhaps @IzzySoft could help here :) |
With what? Any issues with the app in my repo? If it's about F-Droid.org, I'm currently not active there. |
@IzzySoft no issue with the app on izzyondroid. everything perfect ! |
@IzzySoft I hâve one question about metadata. now that to have on this repo separated metadata in two inside fast lane/metadata, how does your updater knows which folder to pick for com.akylas.documentscanner app? |
That's a configuration item on my end. If I shall pick a specific one, let me know which. Other than F-Droid where you need to put it into a specific location or it won't be fetched, in my repo I can define any URL as "Fastlane root" (i.e. the directory where the locale-specific stuff starts; usually |
@IzzySoft OK thanks. so this is the path for the new metadata ( for com.akylas.documentscanner): https://github.com/Akylas/com.akylas.documentscanner/tree/master/fastlane%2Fmetadata%2Fcom.akylas.documentscanner%2Fandroid i am about to release my second app from that repo. will let you know to see If izzyondroid can pick up both apps |
OK, I've adjusted the path here accordingly. But as soon as the second app shows up, we have quite another problem: your tag names. I have no idea if my script can work with the naming pattern you use there. So it has no way to keep the releases of the two apps apart if I cannot pin it to a tag name pattern. Separate apps should use separate repositories. Such mixes lead to complications, earlier or later. And if on each release (or on each second release) I get error mails from my updater and have to adjust manually, I will simply have to disable updates. Wuff. Looks like I've underestimated myself there. I've adjusted the YAML for your app here to AutoUpdateMode: Version ^com.akylas.documentscanner/.+/%c$
UpdateCheckMode: Tags so it should only consider tags matching that regular expression. Then I manually triggered an update check:
I didn't think this would work, but it obviously does – as the log clearly shows it found AutoUpdateMode: Version ^com.akylas.documentscanner/.+/github/[^/]+/%c$
UpdateCheckMode: Tags to skip the betas. Looks like I did a better job with my framework than I knew 🙈 Guess I just never encountered such a tag naming pattern before to test it against… |
@IzzySoft amazing work! yes that github tag filter is perfect! |
If it really works and we do not run into issues, I can hardly object 🙈 So do you want me to nail it to the RegEx above (including the |
@IzzySoft Yes sorry thought you already did start using it. It look perfect. How do you handle alpha/test version? I am thinking of sometimes create a test release just for github with sentry enabled. I would prefer you would not pick it up. |
No, I wasn't sure if that#s what you wanted 😉 Is set up now, and manually triggering an update seems to confirm it works. For real we'll see that as soon as another tag name pattern shows up.
Easiest way to ensure that would be making those "pre-releases". Those are currently skipped for your app. Another variant is using a tag name that doesn't match the RegEx above. If you e.g. use |
@IzzySoft pre release is perfect! thank you ! |
That one was just picked up when I tested the updated RegEx with my comment above 😉
I do not see any pre-release (apart from 1.2.12 build 22, 4 days ago). As you know when you tag such: just check after 7 pm UTC (winter; 6 pm UTC summer) after tagging and you should see if it was picked. |
@IzzySoft awesome. perfect then! |
that's not true: https://f-droid.org/docs/Inclusion_How-To/#reproducible-builds also a rather odd thing to say when this app is signed by Google in their store 🤷
malicious actions towards another FOSS project? Please stop helping. |
@licaon-kter not sure I understand the linked page completely. does that mean we can publish apks directly on f droid without fdroid server rebuilding it all (with dependencies) ? |
@farfromrefug no, F-Droid main repo hosts only FOSS apps. You need to actually be able to build it to say "yes, it is FOSS". If it's reproducible we can use the package signed by the developer. |
@licaon-kter well it is more than building it. it is building it and all its deps. which is not always easy and use a lot of CPU power on each new build. this is why I am sticking with only Izzy for all my Nativescript apps (which are 100% Foss) |
@licaon-kter said:
If you get things from Google, you sign up for several things you as the user should be aware of.
A little general advice:
F-Droid has several positive sides to it and can be considered a good project. My real advice is to not get emotional when you want to achieve something. Emotions can be of great value to motivate and find new ideas. But they may make you blind, less precise and sloppy. Please keep that in mind. As @farfromrefug mentioned, there's several challenges when having someone else build your software. Some Applications may do just fine when build by F-Droid. Others are better built by the developer itself. I updated my previous comment to better reflect on the current subject (also for new visitors to this issue). |
False, c'mon, try harder :)
Not since Nov 2021 or so iirc...
True for older than Nov 2021, yes
True, but the spirit of FOSS is to be able to do it, and not have your "helping hand" sabotaging it. Take it this way: is it FOSS? Great. Can I build it? Ah, no, see, reasons, trust us... Regarding your "ideas", imagine using F-Droid, wanting to install "ThisApp" and F-Droid deciding to install "DifferentApp" because "DifferentApp has developers that actually test code, not release buggy versions that they patch later". My emotions are fine, I fail to see the fairness in the treatment, when F-Droid has an issue "oh my, so problematic", but apps are faultless always? |
You're right. It is now mostly possible to publish apk's built by the developer. Play Store & APK Signing: I checked it again. Keys on Aard2 GitHub release and Play Store version are the same. Same with Vivaldi. I compared using App Manager.
That idea is about letting users who don't know of other repos find software that's to be found elsewhere. But I understand that this is something to be fixed by F-Droid itself (to properly notify users about other repos and available software) and that my suggestion is not a solution. So I removed it.
That's good to hear
What do you mean by fairness? But why would I treat it unfairly when I say that? |
It is not, ask the developers here "Why" they chose Google to sign their APKs. Of note, if the app is build reproducible, F-Droid can only host APKs that are NOT downloaded from Play, as those, signed by Google, would be corrupted with injected proprietary data.
Why would it though? "Hello my name is NA0341, I'm boring so don't speak with me, speak with Izzy instead" right? That's how you work? I hope not...
Somebody asked for its inclusion and you posted a FUD filled rant. Not sure why you did this, did F-Droid kick your dog? If you don't use F-Droid, that is fine, but others do and others might want F-Droid to build this app and host it. Can they get your permission? I hope they do.
Github servers run all the time, Izzy's servers consume power when they grep all the source repos to download APKs, Google Play servers consume serving your app etc. I do understand your concern, but it's a moot point by now.
Node.js is plenty of supported, although F-Droid only hosts one NativeScript app: https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/com.vishnuraghav.EnRecipes.yml#L115-L162 |
@licaon-kter I 100% disagree with your point about energy. you are basically saying we already consume so we dont care if we consume more. but if you both dont. mind let's stop that discussion there on github and let's keep focus on the original subject. Edit : Nativescript has nothing to do with nodejs and that app on fdroid was actually not fully built but accepted mostly as is (the Nativescript runtime was not built). |
So lines 91 to 106 don't build anything? Maybe I've read wrong those
I agree, I only responded because the FUD post was unchallenged by anyone for months, as if the devs here believe the same false information. |
@licaon-kter it does not really build the runtime as in building the core of it. the runtime as it is built. in those lines uses pré built so libs for the actual core of the runtime which is v8. |
Then it will be reviewed and removed |
@licaon-kter well I hope it won't be done for the sake of the developer based on my comment. would be really unfare to him. |
The rules are what they are, things slip, we try to fix them and learn from any mistakes. |
(Looks like somebody deleted their comment 👀)
If issues arising from users for F-Droid then that's the repository owner problem. There are better ways to handle it e.g. pinning an issue. Throwing the problem to F-Droid with dummy app with explanation is an severe issue. I'm sure F-Droid don't wanna handle such users asking about dummy app.
F-Droid never verify other repos, why would F-Droid promote 3rd party repos in their official client? It's the users' choice & responsibility to add/trust other repos. @farfromrefug you may wanted to convert the issue to a discussion since they dragged unnecessary FUD topics about F-Droid. |
@shuvashish76 thanks for commenting. Good idea will do that when I am on my computer. |
No description provided.
The text was updated successfully, but these errors were encountered: