Running the ebuild config to setup a chroot for bind leaves unused files in /etc (dups of what is copied into /chroot/dns/etc/bind) mother bind # diff -ru /etc/bind /chroot/dns/etc/bind/ mother bind # Is there a reason for this? As is, you have a real set of config files, and a in the usual place but not used config files waiting to confuse someone. Why not have /etc/bind symlinked to /chroot/dns/etc/bind?
I don't feel it's either safe or practical to remove any config files in an ebuild. Since files in /etc/ are protected by CONFIG_PROTECT anyways, they become the responsibility of the system administrator. Moreover, if an administrator is chroot()'ing their BIND installation, it is assumed that they are adequately prepared to deal with "orphaned" config files.
