-
Notifications
You must be signed in to change notification settings - Fork 6
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
Podman/Buildah: Add uCPP package via new build-arg #36
Conversation
@iluminae @vrothberg @Luap99 @rhatdan PTAL and LMK if this is good enough. Esp. if the |
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.
LGTM
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.
LGTM, I have not tested this though.
If it helps, I pushed a locally built test-image as |
Since podman supports use of a `#include` directive in `Containerfile` it's prudent to include the tooling necessary to fully make use of this feature. Add a symlink from `cpp` -> `ucpp` as there isn't one by default. Also, since downstream users of the podman image may want a way to more easily customize the package list, de-duplicate the specification via a new build-arg. Signed-off-by: Chris Evich <cevich@redhat.com>
It's unlikely that a full-blown C pre-pocessor is required. My understanding is this package was added in order to support the `Containerfile.in` `#include` feature. This can easily be accomplished with `ucpp` at a greatly reduced overall image size. Realize this effect while de-duplicating the package list via a build-arg. Signed-off-by: Chris Evich <cevich@redhat.com>
Force-push: Switch buildah image from |
Manually tested new podman and buildah images. |
Fixes #35
Since podman supports use of a
#include
directive inContainerfile
it's prudent to include the tooling necessary to fully make use of this
feature. Add a symlink from
cpp
->ucpp
as there isn't one bydefault.
Also, since downstream users of the podman image may want a
way to more easily customize the package list, de-duplicate
the specification via a new build-arg.