Michael Schroeder

Hey, support for alpine has landed a couple of months ago.

I find the use case of trimming every line in the argument somewhat exotic. Having said this, I think you can do that already with the current rpm version: ```...

Your sha256 files contain the full path, which is probably not intended. How about something simpler like: ``` for f in "$BUILD_ROOT/$TOPDIR"/OTHER/* ; do test -f "$f" && chroot "$BUILD_ROOT"...

(This may be a bug, but it's unlikely that it is in obs-build.) You said that you can pull the base container, how do you do that? Can you please...

The base container build should also have produced a `.containerinfo` file. What are the contents of this file?

Hey, where's the `xrepoid` handling? You can't simply delete such things...

Oh, wait, it's there. The inline comments confused me.

Please put `$extrep` in the data hash instead of calculating it again.

And your `createrepo` is actually not the counterpart of `deleterepo`, the counterpart of `deleterepo` is in fact the `publish` function. Your `createrepo` is more like a `createmetadata` function.

Just as data point: SUSE's `build` tool (i.e. like `mock`) has both a `--rpm-build-in-place` and a `--rpm-build-in-place-noprep` option.