I've read the comments on bug 832218 and understand that bind-tools is now just a dummy package that pulls in bind, as it's not feasible to keep them separate. However, it seems that one of the ideas has been abandoned: I would much prefer to have a 'server' USE flag for net-dns/bind, defaulting to on, and when turned off it would not install the files needed to run the 'named' server (but keep all the other tools). Ideally it should not build and install those files at all, but if that's too difficult, it should at least delete them. That would help reduce the clutter. Reproducible: Always
(In reply to aditsu from comment #0) > I've read the comments on bug 832218 and understand that bind-tools is now > just a dummy package that pulls in bind, as it's not feasible to keep them > separate. > However, it seems that one of the ideas has been abandoned: I would much > prefer to have a 'server' USE flag for net-dns/bind, defaulting to on, and > when turned off it would not install the files needed to run the 'named' > server (but keep all the other tools). > Ideally it should not build and install those files at all, but if that's > too difficult, it should at least delete them. That would help reduce the > clutter. > > Reproducible: Always The idea was rejected because manually deleting the right files is brittle, and you'd be compiling the same code anyway. You can use INSTALL_MASK if you want that, at your own risk.
On the off chance that all you are looking for is "dig", the "drill" program from net-libs/ldns is a pretty good replacement.
