Closed zipkid closed 8 years ago
bind
and bind::updater
are intended to be mutually exclusive.
Why intentionally create conflict? Especially since both, now conflicting, classes install the same package....?
Ok, so I'm looking at #78 and thinking to myself "Does this actually fix it?" because years ago I tried to and it was a complete mess. Then I realized, bind::defaults
which both bind
and bind::updater
inherit no longer has resources in it, and bind::keydir
is a lot simpler than it used to be. It was less about intent and more about the big hurdles that stood in the way.
Let's move the discussion to #78
When applying bind::updater on all nodes this causes conflicts on the bind server.