On Sun, Jan 06, 2008 at 11:04:42AM -0700, LaMont Jones wrote: > On Mon, Aug 06, 2007 at 02:42:27PM -0400, Ross Vandegrift wrote: > > On Mon, Aug 06, 2007 at 12:11:46PM -0600, LaMont Jones wrote: > > > On Mon, Aug 06, 2007 at 12:02:24PM -0400, Ross Vandegrift wrote: > > Shouldn't adding libpq-dev to the build-dep only require the pgsql > > libraries? I haven't had too much deb building experience: that was > > my intention. The various DLZ backends are statically linked into > > named at build-time, so seperate packages would be required. > > The backend access shared libs are linked into bind. If the backend > code were statically linked, that would be sufficient reason to reject > things out of hand. > > With the change, 9.4.2 Depends on: > libbind9-30, libc6 (>= 2.7-1), libdb4.2, libdns32, libisc32, libisccc30, > libisccfg30, libldap2 (>= 2.1.17-1), liblwres30, libmysqlclient15off (>= > 5.0.27-1), libpq5, libssl0.9.8 (>= 0.9.8f-1), unixodbc (>= 2.2.11-1), > zlib1g > > which is much too heavy weight for the stock package. so the question > becomes, do we want to have one bind9-dlz package that scrapes all > those dependencies in, or do we want to additionally have some subset > that only scrape in certain pieces? (many admins have issues with "that > other SQL implementation", for example.)
In all honestly, this isn't too relevant for me anymore - my installation is on a long-term track toward powerDNS. DLZ isn't too long for my world :-) Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
