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

buildozer.spec - requirements - kivy == master #440

Closed
youpsla opened this issue Dec 21, 2016 · 3 comments
Closed

buildozer.spec - requirements - kivy == master #440

youpsla opened this issue Dec 21, 2016 · 3 comments

Comments

@youpsla
Copy link

youpsla commented Dec 21, 2016

When using kivy == master (with newtoolchain) in buildozer.spec, version 1.9.1 is downloaded. I've read somewhere that this option should download and compile the current master branch on github which is currently 1.9.2-dev0. In the kivy recipes of python-for-android, the init.py file has a hard reference to 1.9.1.

Is it normal behavior ?

Anybody has a solution for packaging latest master ?

@KeyWeeUsr
Copy link
Contributor

The recipe should fetch the version according to the value in buildozer, at least that was the way how old recipes worked. Try to print the url if the version was changed to .../archive/master... or not.

Also, the latest master doesn't work right now, because of some changes of compilation (see kivy/kivy#4832 ), therefore if you really need master, your best guess is to use latest commit without those changes. It should work even with replacing version with the hash.

@youpsla
Copy link
Author

youpsla commented Dec 21, 2016

Thanks KeyWeeUsr.

I'll go step by step into your solution and keep in touch.

@tito
Copy link
Member

tito commented May 15, 2017

When you do kivy==master, it won't redownload or check if master changed between your latest download of kivy and the spec. Just clean the cache, and it will redownload according to your requirements

@tito tito closed this as completed May 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants