ebuild doesn't initialize the $EXISTS var. So when I run "emerge /var/db/pkg/net-dns/bind-9.2.2_rc1-r2/bind-9.2.2_rc1-r2.ebuild config" a first time and the $CHROOT dir exists, when you delete the dir and run it again the $EXISTS var will be set to "yes" and the script will fail without any warnings. A simple $EXISTS="no" in the beginning will solve the problem. Reproducible: Always Steps to Reproduce: 1. set CHROOT="/chroot/dns" in /etc/conf.d/named 2. mkdir -p /chroot/dns 3. emerge /var/db/pkg/net-dns/bind-9.2.2_rc1-r2/bind-9.2.2_rc1-r2.ebuild config 4. rm -rf /chroot/dns 5. emerge /var/db/pkg/net-dns/bind-9.2.2_rc1-r2/bind-9.2.2_rc1-r2.ebuild config Actual Results: It won't report any error (nor any output whatsoever) and won't configure the chroot dir. Expected Results: Configure the /chroot/dns dir tree to suport chrooted bind. It was a clean gentoo instalation.
shouldn't it be ebuild .... config anyway instead of emerge .... config?
good point fixed in cvs thx
*** Bug 18629 has been marked as a duplicate of this bug. ***