3 ms·
>(At the time I set up my RPM configuration, the default RPM setup of package source wasn't ideal because it could comingle components of all packages together.
by Arnavion 3y ago
>(At the time I set up my RPM configuration, the default RPM setup of package source wasn't ideal because it could comingle components of all packages together. These defaults may have changed since then.)
It's still the same unless you manually make the effort to use a different topdir for each build.
>Neither RPM nor Debian packages provide hermetic builds out of the box. For RPMs, mock provides an all-in-one solution that's generally very easy to use.
You set up a chroot / container and build inside that. For OpenSUSE, the `osc build` command wraps `rpmbuild` to do that, and...
>Debian has the sbuild collection of tools (also, sbuild(1)) that, based on my reading, provide the tools you need to do this (I only recently found out about sbuild and haven't tried to use it).
... according to its documentation that's what sbuild does too. Though the author's concern is also about how easy to use it is, which I have no experience with. My Debian packaging experience has been to use dpkg-buildpackage in a container.
- snuxoll 3y agoFor RPM's you would use mock (https://rpm-software-management.github.io/mock/ https://rpm-software-management.github.io/mock/) to handle reproducible/hermetic build environments; it's the underlying tool used by Koji (the Fedora and Red Hat package build system) so it's regularly getting the tires kicked too.