I just found that chroot_safe is a very handy app and it's be nice if it's in portage. you can forward all bug reports to me (or contact me on irc) Reproducible: Always Steps to Reproduce: 1.emerge -p chroot_safe Actual Results: emerge: there are no ebuilds to satisfy "chroot_safe". Expected Results: [ebuild N ] app-admin/chroot_safe-1.3 0 kB
Created attachment 39669 [details] chroot_safe-1.3.ebuild Please note that export CPPFLAGS="${CXXFLAGS}" is needed or else it'd ignore the CXXFLAGS for building. Also the sed line is needed because the script has a hardcoded lib path and it must run after econf finishes.
I don't see a point in this ebuild as app-admin/chrootuid already exists in the tree. Reassinging to bug-wranglers
chroot_safe does a runtime setup of required shared libraries, so there is no need to install all dependant libraries inside the chroot, as it is required with chrootuid. You don't even need to install the binary inside the chroot, to let it run chrooted. In my eyes chroot_safe should be preferred over chrootuid.
Added as app-admin/chroot_safe. Thanks for the report.
