Skip to content
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

Check metadata of c:geo fdroid repo #7403

Open
Lineflyer opened this issue Mar 20, 2019 · 6 comments
Open

Check metadata of c:geo fdroid repo #7403

Lineflyer opened this issue Mar 20, 2019 · 6 comments
Assignees
Labels
CI server / Build tools Issues with our CI server or other build/dev tools

Comments

@Lineflyer
Copy link
Member

Can someone enlighten me, if and how we can edit the content of our fdroid repository.
Specifically not the packets/APKs itself, but things like description and donation links.

@kumy ?

@Lineflyer Lineflyer added Feedback required Issue requires feedback of the author or another user CI server / Build tools Issues with our CI server or other build/dev tools labels Mar 20, 2019
@kumy
Copy link
Member

kumy commented Mar 20, 2019

@Lineflyer It should those files https://github.com/cgeo/cgeo-fdroid/tree/master/fdroid/metadata
Then I have to pull and rebuild images here ;)

@Lineflyer
Copy link
Member Author

Thanks for the information. Will review it as time permits.

@Lineflyer Lineflyer changed the title How to maintain/edit the c:geo fdroid repositories Check metadata of c:geo fdoird repo Mar 20, 2019
@Lineflyer Lineflyer self-assigned this Mar 20, 2019
@Lineflyer Lineflyer removed the Feedback required Issue requires feedback of the author or another user label Mar 20, 2019
@Lineflyer
Copy link
Member Author

Lineflyer commented Mar 20, 2019

Are different languages supported on fdroid?

@kumy
Copy link
Member

kumy commented Mar 20, 2019

@rsudev rsudev changed the title Check metadata of c:geo fdoird repo Check metadata of c:geo fdroid repo Mar 23, 2019
@Lineflyer
Copy link
Member Author

@kumy
Coming back to this issue (and regarding localization). According to your links above the localization requries a dedicated dir structure starting with package-id, then locale, etc.

At the moment I do only find the single description. What needs to be done to support the structure required (I have no idea about dockers and how this works here)?

@kumy
Copy link
Member

kumy commented Jul 15, 2020

I'll make some test to check/find the right directory structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI server / Build tools Issues with our CI server or other build/dev tools
Projects
None yet
Development

No branches or pull requests

2 participants