Date: Tue, 23 Feb 2021 16:05:12 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 253799] dns/bind916: master/slave -> primary/secondary Message-ID: <bug-253799-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253799 Bug ID: 253799 Summary: dns/bind916: master/slave -> primary/secondary Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: mat@FreeBSD.org Reporter: freebsd@ohreally.nl Flags: maintainer-feedback?(mat@FreeBSD.org) Assignee: mat@FreeBSD.org Bind has switched terminology from master/slave to primary/secondary. https://bind9.readthedocs.io/en/v9_16_12/introduction.html?highlight=3Dprim= ary#the-primary-server When using this more modern terminology it makes sense to also change the n= ames of the directories 'master' and 'slave' to 'primary' and 'secondary', which= I did. I would appreciate it if the make options for the port could include options like (*) Use primary/secondary terminology ( ) User master/slave terminology This would avoid the creation of new directories named 'master' and 'slave' when updating, as well as the installation of new 'empty.db' and 'localhost-*.db' files in unused directories. On the other hand, it would s= till allow existing installations to continue using the old terminology, if desi= red. Since Bind now prefers the use of primary/secondary, it would probably also make sense to use these terms as the default for new installs. Thanks, Rob --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253799-7788>