Am Montag, 14. Februar 2011, 13:26:32 schrieb Jeff Johnson:
> Yes but ... rpmbuild --root is not doing chroot(2), never has done
> chroot(2), and cannot do chroot(2) unless uid == 0.
The latter one I solved by calling "sudo rpmbuild".
> It in the man page because someone insisted:
> Its a CLI option so it MUST be in the man page.
> and it was easier to oblige than explain.
What's the difference between '--root' and '--dbpath' then?
> File path's get implicitly prefixed when chroot(2) is called.
> There's harder issues, like readong configuration (from inside or outside
> the chroot?) and finding the rpmdb (inside or outside?) and writing *.rpm
> output (inside or outside), but otherwise yes.
I can answer these questions in case of what I'm planning to do. I mainly
don't want to populate the buildroot with all dependencies of RPM, that's all.
But I can live with copying macro files and other config data.
Ok, off trying... :-)
Received on Mon Feb 14 14:31:44 2011