-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
outdated recipes #2277
Comments
Yes please go-ahead with the update. The best practice is for users to pin recipe version in their buildozer.spec if they want to be sure it doesn't get updated 😄 |
I don't recall seeing an option to pin recipes. How does one do that? |
The same way you pip install a pinned package. So basically users should pin versions in their requirements list if they want to, e.g. https://github.com/AndreMiras/EtherollApp/blob/v2020.0322/buildozer.spec#L40 |
Ah. I mistakenly assumed that only worked for pip dependencies, not for p4a recipes. Good to know! |
I've started working on a script to check for updates in e.g. p4a recipes.
|
I'd be happy to make some PRs for newer versions. Currently outputs:
|
Sweet! Can't think of any specific priority.
|
Any way to know which recipes are used a lot? |
I've also added a command to check for updates to (pinned) recipes (and pypi packages without recipes) in a
Unfortunately it might be a while before I have time to properly document & package the script so others can use it easily. |
We don't have a stats on used recipes yet, so I also think updating the ones you use yourself is a good approach. |
Closing - there is good discussion here, but no action required by python-for-android team. |
Because many of the recipes I use have outdated versions (which may also have security implications), I'm currently building the following recipes with a patch to use the latest version (as of a week or so ago):
flask hostpython3 libffi openssl pyjnius python3 setuptools six sqlite3
.So far everything works for me without any problems (other than #2264).
I'd be happy to make PRs for those, but the latest versions may break for some users (and build environments).
What's the best/preferred way to handle this?
The text was updated successfully, but these errors were encountered: