-
Notifications
You must be signed in to change notification settings - Fork 245
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
Filter intermediate links by architecture #2162
Comments
It seems I'm not allowed to reopen a closed issue, which I find a bit strange, it seems to me that reopening this issue would be more appropriate than opening a new issue for this, so I'll just post here anyway, and if it doesn't get any response after a while, I'll escalate it to a new issue. Anyway... @ImranR98: Please consider changing the name (and associated JSON key) of this option in the locations where it applies to a list of intermediate links to Note: I was planning to submit some updates to the Crowdsourced App Configs list to make use of this feature (huge thanks for implementing it!) but felt the naming was confusing and should be changed, and felt that if it does get changed, it would be better to wait till the change happened to submit my app config updates, so they won't need to be updated again for this change. Thank you! [Edit: New issue opened. See #2182.] |
Feature Description:
I'd like to be able to filter intermediate links by architecture, similar to the existing "Attempt to filter APKs by CPU architecture if possible" option.
I'm unsure if it would be best to add this functionality to the existing option, or to add a new option to 'filter intermediate links by architecture'. Also, if adding a new option is preferred, I wonder if it would be better to add a single option next to the existing one, which applies to all defined intermediate links, or if adding the option to each intermediate link's definition would be preferred. Any of these options would satisfy my request.
Rationale:
There are some apps which are distributed via sites that are currently best suited to using the HTML source type, where the APK files for different architectures are kept in different locations. This makes the current 'filter APKs by architecture' unusable for these apps.
Example Use Case:
If I go to the list of Crowdsourced App Configs and search for Firefox, all of the listings for the official Firefox options have a separate config for each of the listed architectures, and the less popular apps (Focus & Klar) only have one architecture listed. If there was an option to filter intermediate links by architecture, each of these listings could be reduced to a single config where the user's installation of Obtainium could detect the correct architecture automatically, just like it does with apps where the APKs for all architectures are published together.
The text was updated successfully, but these errors were encountered: