-
Notifications
You must be signed in to change notification settings - Fork 523
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
Docker from current git #775
Conversation
Yes, I'm Lukasz Mach and I don't know why it took my Name/Surname instead of nick. Probably infected with my other settings. Re commit - how can I remove it? This commit is based on #773, I believe that once #773 is merged to master, then this commit will disappear from list of commits and from diff. |
Ok, just wanted the confirmation. About that commit, you can do
to save all your unsaved changes to stash, remove the two commits (but leave the changes available), add only the Docker related changes, create a clean commit, force push to this branch (you have a different branch for PR #773) and retrieve back the saved changes from stash. Also, don't add unnecessary spaces on this line 7158ceb#diff-2eeaed663bd0d25b7e608891384b7298R47. Otherwise the (docker related) changes are fine and I'd merge them. I'm not sure about NDK changes, that's why I want to remove the previous commit :) |
7158ceb
to
2be2d77
Compare
ok, so I did like you said. It's not exactly clear what do those commands do, but apparently they work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me, also it's good to have most likely an import error fixed with the missing sh
requirement included.
I wonder if the code that uses sh
was only recently included or whether it just silently failed because p4a included that dependency too.
@@ -44,10 +44,10 @@ def find_version(*file_paths): | |||
license='MIT', | |||
packages=[ | |||
'buildozer', 'buildozer.targets', 'buildozer.libs', 'buildozer.scripts' | |||
], | |||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please remove this empty change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I also got bugged by it, but I tried to not say anything because I'm always the one nit picking 😛
So sorry if I saw your comment before I would not have merged 😕
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good to me, thank you
Yes @KeyWeeUsr the
@mahomahomaho yes git squashing and rebasing looks awkward at first, but it's actually a pretty awesome thing to know and use |
it's nice to build docker with current, bleeding edge or even uncommited version of buildozer, instead of using only stable, pypi pushed buildozer version.
In such case, --build-arg git=true should be used.