If you’ve ever wondered what packages are needed to build a DragonFly release: here they are in one dports metapackage.
3 Replies to “Tools for building DragonFly”
Comments are closed.
A running description of activity related to DragonFly BSD.
A running description of activity related to DragonFly BSD.
If you’ve ever wondered what packages are needed to build a DragonFly release: here they are in one dports metapackage.
Comments are closed.
It’ s not the packages needed to build a release, it’s the packages that _we ship with a release_.
bind-tools isn’t needed at all to build a release (you added it, remember?), but it’s convenient to have because it might be useful when setting up the network to get into a state where you can install additional packages.
OK if it is meant like “nrelease will fail when one of these fails”, then you are correct. :)
nrelease == release for me, cause that’s the form it takes for me most often. I didn’t mean to imply we had that dependency just to do a buildworld/buildkernel cycle, though it certainly could be read that way; my bad.