Include the commit of the build (if available in the build environment),
also include the version of `images` in the build; if available.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
The Go macros have a bunch of expectations about package names and
archive names. Let's keep the archive names with `-cli` in them to
appease them.
These can only be dropped after we change repositories around and thus
change the `goipath`; after which these can drop their `-cli`.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
`image-builder` will be the main entrypoint into the Image Builder
stack. We will rename the repositories later on; but let's start
referring to it in its new official name.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
For releases this does not change anything, as the version
in the spec file is the same as the git tag. For
intermediate/tainted versions packer seems to patch the spec
file to the version given in `.packit.yaml`
(which is the latest git-tag), then the filename and version
would be inconsistent.
RPM tooling expects the source tarball to match the name of the
package, suffixed with the version in the SPEC file. Modify the Makefile
to comply with this expectation.
Signed-off-by: Tomáš Hozza <thozza@redhat.com>
Provide a spec file for `image-builder-cli`. The spec file is based on
`osbuild-composer`'s spec file except it is simplified as (some)
usecases would currently cloud the intent of the specfile. We can add
back RHEL conditionals when/if we start shipping and building for RHEL.
Some tools from `osbuild-composer` are also included; most notably the
one that generates bundled dependencies from vendored modules.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
