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

Kivy Android VM doesn't have plyer recipe #239

Closed
trivedigaurav opened this issue May 20, 2014 · 3 comments
Closed

Kivy Android VM doesn't have plyer recipe #239

trivedigaurav opened this issue May 20, 2014 · 3 comments

Comments

@trivedigaurav
Copy link
Member

The Kivy VM link available at from readthedocs does not have a plyer recipe. Although you can get over this issue by updating the repo, steps like this defeat the purpose of having a virtual image.

@brousch
Copy link
Contributor

brousch commented May 20, 2014

That VM image actually pre-dates the creation of Plyer. It also comes with
Kivy 1.5.2. Following the README updte instructions should bring it up
tothe current stable versions.
On May 19, 2014 11:11 PM, "trivedigaurav" notifications@github.com wrote:

The Kivy VM link available at from readthedocshttps://doc-10-94-docs.googleusercontent.com/docs/securesc/mmjp9iu6bv6d8br5gnce6iipsdfcijja/5a3kq2v90h7vo69mfa63le47a5vthod3/1400551200000/14602018143709242860/11676337812890946758/0B1WO07-OL50_bTR0SElrLTZGWEU?e=download&h=16653014193614665626&nonce=dut7qck1i1o0s&user=11676337812890946758&hash=o07p3auqb29img7ov20ks3se6unk64a6does not have a plyer recipe. Although you can get over this issue by
updating the repo, steps like this defeat the purpose of having a virtual
image.


Reply to this email directly or view it on GitHubhttps://github.com//issues/239
.

@trivedigaurav
Copy link
Member Author

@brousch Yes, I understand that. I was wondering if it would be possible to include a last known working versions for p4a / kivy / plyer. Since, the VM offers a failsafe way of running things, this way it would be useful to point out any recent regressions in the code as well.

@tito
Copy link
Member

tito commented May 27, 2014

It is hard for us / impossible to have continuous integration with the VM. VM takes lot of times to build , compress, and upload. This is why we prefered to include a README and let you update it. I guess we could provide a packer.io script instead for building it yourself.

@tito tito closed this as completed May 27, 2014
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