From: gvccandido <gvccandido@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] nsupdate under bind-utils
Date: Fri, 17 Mar 2023 23:00:46 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42825@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
New issue by gvccandido on void-packages repository
https://github.com/void-linux/void-packages/issues/42825
Description:
Is there any reason for `nsupdate` to be under `bind` package and not under `bind-utils`? The latter is usually the case for other distributions and as far as I can see there should be no other dependencies for it than what is already used by `bind-utils`.
If there is no reason, I believe the only needed changes are including `nsupdate` binary and manpage to `bind-utils` definition at [template file](../blob/master/srcpkgs/bind/template), under `bind-utils_package` function.
next reply other threads:[~2023-03-17 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 22:00 gvccandido [this message]
2023-06-16 1:59 ` github-actions
2023-06-23 20:03 ` [ISSUE] [CLOSED] " Duncaen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42825@inbox.vuxu.org \
--to=gvccandido@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).