Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
WIP: Support more bind9 utilities #1321
base: main
Are you sure you want to change the base?
WIP: Support more bind9 utilities #1321
Changes from 3 commits
e5ce915
9c16c37
5f92262
8c1eac9
8f3a039
2c119dc
5668561
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function is defined in another file, which may not be loaded in the session. One needs to "export" the function by renaming
_comp_cmd_nslookup__queryclass
to_comp_xfunc_nslookup_compgen_queryclass
and call it using_comp_compgen -x nslookup queryclass
.This means that we need to modify
bash-completion
too even if we'd include the completion settings to the upstream.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, yes. unless we would rely on named-rrchecker providing list of supported types. That does not come with common package containing utilities only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
further more, it might be useful also for ldns
drill
tool orunbound-host
. Even though better would be getting actually supported list from the tools itself, we do not have it always at hand.But the question is, whether it would not make sense to move nslookup functions into the bind9 as a whole. They are after all bind9 utilities in normal circumstances.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We haven't been officially doing that when there are multiple implementations for a specific command name, but I think it would make sense. We should still keep our current implementation of
completions/nslookup
atcompletions/_nslookup
for the other implementations ofnslookup
. We've been regarded ourcompletion/_<cmd>
completion settings as "deprecated" completion which should be replaced by the newer implementation of the upstream completion settings, but the present suggestion is to usecompletion/_<cmd>
as the "default" completion settings when a specific completion setting is not provided by the upstream project. Or we might add even another form of the completion files for the "default" completion or another directory for the "default" completion. Thus, your suggestion involves a reconsideration of our framework about the role of ourcompletion/_<cmd>
settings or introduction of the mechanism of defining the "default" completion.