Comments on: Tools for building DragonFly https://www.dragonflydigest.com/2018/05/23/tools-for-building-dragonfly/ A running description of activity related to DragonFly BSD. Wed, 23 May 2018 16:30:20 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Justin Sherrill https://www.dragonflydigest.com/2018/05/23/tools-for-building-dragonfly/comment-page-1/#comment-487374 Wed, 23 May 2018 16:30:20 +0000 https://www.dragonflydigest.com/?p=21287#comment-487374 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.

]]> By: Sascha Wildner https://www.dragonflydigest.com/2018/05/23/tools-for-building-dragonfly/comment-page-1/#comment-487373 Wed, 23 May 2018 05:59:53 +0000 https://www.dragonflydigest.com/?p=21287#comment-487373 OK if it is meant like “nrelease will fail when one of these fails”, then you are correct. :)

]]> By: Sascha Wildner https://www.dragonflydigest.com/2018/05/23/tools-for-building-dragonfly/comment-page-1/#comment-487372 Wed, 23 May 2018 05:57:46 +0000 https://www.dragonflydigest.com/?p=21287#comment-487372 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.

]]>