public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why does bind-tools 9.18 depend on bind?
Date: Sat, 26 Oct 2024 11:40:18 +0200	[thread overview]
Message-ID: <671cb905.5d0a0220.245097.d74f@mx.google.com> (raw)
In-Reply-To: <2acf0931-8d75-4e2d-99f2-75a8f8fcd94e@gentoo.org> (message from Matt Jolly on Fri, 25 Oct 2024 08:35:00 +1000)

Matt and others,

On Fri, 25 Oct 2024 08:35:00 +1000 Matt Jolly wrote:
> ...
> On 25/10/24 04:45, Grant Edwards wrote:
> > ...
> > What's so special about bind-tools 9.18 that it has to have bind
> > installed?
> 
> The commit that added 9.18.0[1] gives some context:
> 
>   >This is just a proxy for net-dns/bind. Splitting the ebuilds is *way* too
>   >fragile and gains nothing because the same software gets built again 
> anyway,
>   >just thrown away at the end.

Doesn't that mean  that best practice  would be  to just ditch "net-dns/
bind-tools" and solely install  "net-dns/bind" instead?   At least up to
now the latter _also_ provides "nslookup" and "dig".

Sincerely,
 Rainer


  parent reply	other threads:[~2024-10-26  9:40 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
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   ` Dr Rainer Woitok [this message]
2024-10-26  9:54     ` [gentoo-user] " 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=671cb905.5d0a0220.245097.d74f@mx.google.com \
    --to=rainer.woitok@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