From: "Thomas T. Veldhouse" <veldy@veldy.net>
To: "Stroller" <gentoogimp@myrealbox.com>, <gentoo-dev@gentoo.org>
Cc: <stroller@bigfoot.com>
Subject: Re: [gentoo-dev] ISC-Bind inconsistancy
Date: Sun, 16 Mar 2003 09:37:52 -0600 [thread overview]
Message-ID: <000901c2ebd2$01fecad0$0101a8c0@cascade> (raw)
In-Reply-To: 1047685726.b6bb4300gentoogimp@myrealbox.com
----- Original Message -----
From: "Stroller" <gentoogimp@myrealbox.com>
To: <gentoo-dev@gentoo.org>
Cc: <stroller@bigfoot.com>
Sent: Friday, March 14, 2003 5:48 PM
Subject: Re: [gentoo-dev] ISC-Bind inconsistancy
>Whilst I can't comment on your other points, I supect that the short answer
to this last is >because "that's the way that Berkeley (?) package them'.
Uhm -- no they didn't. They are in the same source tarball.
>I can see good reason for having 2 separate packages: Joe User buys his DNS
hosting >service from ISP.net, as he lives out in the country & can't run a
24/7 Bind server (his >servers are at another.isp.net & bigISP.com). He
wants to query his DNS config >periodically, however, to check it, and so he
can make requests to >customer.admin@ISP.net; consequently Joe User needs
Bind-tools, but not Bind itself.
I can not. The size of the additional named binary is small. Very small.
The cost of building the entire package twice is much bigger. I can see
having a separate package that installs only the tools, but I can not see
having the bind package not install the tools in the first place.
Tom Veldhouse
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-03-16 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 23:48 [gentoo-dev] ISC-Bind inconsistancy Stroller
2003-03-16 15:37 ` Thomas T. Veldhouse [this message]
2003-03-16 19:52 ` Stroller
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 17:34 Thomas T. Veldhouse
2003-03-14 20:26 ` Norberto BENSA
2003-03-14 21:06 ` Max Kalika
2003-03-14 22:44 ` Norberto BENSA
2003-03-16 15:38 ` Thomas T. Veldhouse
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='000901c2ebd2$01fecad0$0101a8c0@cascade' \
--to=veldy@veldy.net \
--cc=gentoo-dev@gentoo.org \
--cc=gentoogimp@myrealbox.com \
--cc=stroller@bigfoot.com \
/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