Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommendation for bind module is troublesome #4

Open
daenney opened this issue May 9, 2014 · 2 comments
Open

Recommendation for bind module is troublesome #4

daenney opened this issue May 9, 2014 · 2 comments

Comments

@daenney
Copy link

daenney commented May 9, 2014

The documentation contains:

bind9::params
postgresql-8::service
mysql5::install

As examples of bad module names. In the case of MySQL and Posgresql I can agree but not in the case of bind. There's a huge different between bind9 and bind10, they're very different software project which can also be run together. Having modules only use the name 'bind' is going to confuse and trip up people.

As far as I'm concerned they shouldn't have named it BIND 10 but something else entirely because it's a completely different architecture but we're stuck with it.

@jhoblitt
Copy link

jhoblitt commented May 9, 2014

FYI - bind10 has been renamed to "bundy". http://bundy-dns.de/

@alvagante
Copy link
Contributor

This might be an edge case, but seems like the bundy (horrible) name may solve such a dilemma.
The principle of not having version numbers in modules names I think is obvious and widely used.
Exceptions might be addressed in some way (for my point of view any way is good if it's shared)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants