Re: Why Does bind Have So Many Dependencies

On Sat, Mar 16, 2024, at 11:30, Tim Daneliuk wrote:
> On March 15, 2024 6:23:11 PM Lowell Gilbert 
> <freebsd-questions-local@be-well.ilk.org> wrote:
>
>> Tim Daneliuk <tundra@tundraware.com> writes:
>> 
>>> I got notice the bind 9.16 was going EOL and to upgrade to 9.18.
>>> 
>>> When I built from source, I saw this very long list of other stuff
>>> that got build.  X libs?  doxygen?   Why  all this:
>> 
>> Offhand, I can say that's not a particularly heavy set of dependencies. A
>> lot of them look like they probably come from something along the line using
>> a lot of rendering tools to build its documentation.
>> 
>> Why do you ask? After all, you're clearly pretty competent at dealing with
>> the ports system.
>> 
>> Be well.
> Because I try to not clutter up servers with unnecessary ports.  It 
> takes up space and increases the attack surface.
>
> What I don't understand is that I told the build not to include docs 
> but it installed all this other cruft anyway. 
>
>  A dns server build shouldn't require groff and xaw...

To rebuild the manpages and other documentation from source requires groff and a few other tools. Portmaster can uninstall build dependencies that aren’t in the run dependencies list after installation of the port. ```pkg autoremove``` will also remove unneeded build dependencies. The last option is using poudrière. ```pkg install``` will only pull in the needed runtime dependencies.

I am assuming don’t want to use the default package repository.