[Rpm-maint] [rpm-software-management/rpm] Removing --clearenv, because bubblewrap 0.4.0 does not support it (PR #2658)

[Michal Domonkos]

Indeed, `--clearenv` is there to ensure we run the tests in a clean environment. It also means we don't have selectively unset the various env vars in the container that could interfere with the test. The current tests *might* still work even without `--clearenv` but we don't want to change that now.

For now, to run the tests, you can configure your build with `cmake -DMKTREE_BACKEND=podman` which only requires podman and not bwrap. Note though that this backend will build RPM in a Fedora container so it will *not* test your local build. It's also currently not optimized for development as it rebuilds "too much" on each `make check` invocation.

Another option is to build a more modern version of bwrap from [source](https://github.com/containers/bubblewrap), it's actually a pretty small project with few dependencies and builds quickly.

For the record, we're currently [working](https://github.com/rpm-software-management/rpm/issues/2643) on a unified backend that will get rid of distro-specific scripts and only use podman images. Bubblewrap may or may not be required on the development system, I'm still not entirely sure.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2658#issuecomment-1717195132
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/2658/c1717195132 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20230913/5a9884b0/attachment.html>