From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Why does bind-tools 9.18 depend on bind?
Date: Fri, 25 Oct 2024 13:53:05 -0000 (UTC) [thread overview]
Message-ID: <vfg7s1$17he$1@ciao.gmane.io> (raw)
In-Reply-To: ZxtsCxTwb1jccy2_@stitch
On 2024-10-25, Michael Orlitzky <mjo@gentoo.org> wrote:
> On 2024-10-25 00:47:27, Grant Edwards wrote:
>> >
>> > Try net-dns/doggo[2]
>>
>> Cool, and it doens't want to install 4 other new packages like
>> bind-tools does. [OK, two are just account/group packages, so it's
>> not quite as bad as it sounds.]
>
> It's a Go package though, so it will quietly install a mountain a
> random outdated static libraries from github.
>
> Try it:
>
> $ emerge --fetchonly --nodeps doggo
> $ tar -tf /var/cache/distfiles/doggo-1.0.5-deps.tar.xz
Holy shit! Over 6000 source files.
> BIND may actually be the least bad option.
Indeed.
> The Knot DNS server provides alternatives like kdig, but you'll
> still wind up with a full-fledged DNS server on your hands.
>
> Depending on how serious this is, you could use package.provided and
> INSTALL_MASK to block everything you don't want.
It's probably not worth that much effrot...
--
Grant
next prev parent reply other threads:[~2024-10-25 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 18:45 [gentoo-user] Why does bind-tools 9.18 depend on bind? Grant Edwards
2024-10-24 22:35 ` Matt Jolly
2024-10-25 0:47 ` [gentoo-user] " Grant Edwards
2024-10-25 9:59 ` Michael Orlitzky
2024-10-25 11:08 ` Holger Hoffstätte
2024-10-25 15:59 ` Michael Orlitzky
2024-10-25 16:39 ` Grant Edwards
2024-10-25 13:53 ` Grant Edwards [this message]
2024-10-26 8:10 ` Eray Aslan
2024-10-26 10:42 ` Peter Humphrey
2024-10-27 8:59 ` Eray Aslan
2024-10-26 9:40 ` [gentoo-user] " Dr Rainer Woitok
2024-10-26 9:54 ` Matt Jolly
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='vfg7s1$17he$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.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