Bug 253799 - dns/bind916: master/slave -> primary/secondary
Summary: dns/bind916: master/slave -> primary/secondary
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Mathieu Arnold
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-23 16:05 UTC by Rob LA LAU
Modified: 2021-02-23 16:05 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (mat)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rob LA LAU 2021-02-23 16:05:12 UTC
Bind has switched terminology from master/slave to primary/secondary.
https://bind9.readthedocs.io/en/v9_16_12/introduction.html?highlight=primary#the-primary-server

When using this more modern terminology it makes sense to also change the names 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 still allow existing installations to continue using the old terminology, if desired.

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