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
Wire hab-pkg-export-docker
into hab
& setup for building.
#3334
Conversation
This change performs the same install-on-use logic as `hab sup` and `hab studio` subcommands. The underlying program, `hab-pkg-export-docker` will be directly invoked and therefore: ``` hab pkg export docker --help ``` Will return the usage from `hab-pkg-export-docker` in the `core/hab-pkg-export-docker` package The `exec_subcommand_if_called()` function in the main module was widened to look at 3 subcommands deep, rather the 2 subcommands prior to this change. This was necessary as due to the subcommand depth of `hab pkg export docker`. Future exporters should not need to do this. Signed-off-by: Fletcher Nichol <fnichol@nichol.ca>
This change swaps out the building of `pkg-dockerize` for `pkg-export-docker`, meaning that unstable builds and releases will start building the new component. Signed-off-by: Fletcher Nichol <fnichol@nichol.ca>
Thanks for the pull request! Here is what will happen next:
Thank you for contributing! |
I'm going to take a quick swing at compiling on macOS to confirm the Mac behavior (warn and quit). |
let command = match henv::var(EXPORT_CMD_ENVVAR) { | ||
Ok(command) => PathBuf::from(command), | ||
Err(_) => { | ||
init(); |
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.
Should we be starting this earlier in the function? I think I made changes recently so this wouldn't panic if you called it more than once - can't remember exactly
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.
We could do a future refactor which just jams that early in hab
. We need this for the install logic/verify code and have been only calling it when necessary. But yeah, I've never been 100% happy with that. It's possible that the overhead of that call is so small that it isn't an issue.
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.
Merge when you've done your testing, it looks like a clean replacement to me!
I should note that for the moment, I left |
Took me a couple of tries on my rebuilt macOS to make sure I had all linked library deps. Looks good though. @thesentinels approve |
🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests. |
Travis CI has started testing this PR. |
💖 Travis CI reports this PR passed. It always makes me feel nice when humans approve of one anothers work. I'm merging this PR now. I just want you and the contributor to answer me one question: |
There are a few changes in this PR, split out to make things a bit clearer.
dockerize
.hab pkg export
logic..travis.yml
.