Bug 1329348 - GeoIP dependencies
Summary: GeoIP dependencies
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Hozza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 17:05 UTC by Harald Reindl
Modified: 2016-04-25 08:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-25 08:52:46 UTC
Type: Bug


Attachments (Terms of Use)

Description Harald Reindl 2016-04-21 17:05:10 UTC
bad enough that now everybody is forced to pull GeoIP if installing a nameserver instead a subpackage, but for bind-utils that's cleary ridicolous

[harry@srv-rhsoft:~]$ ldd /usr/bin/nslookup
        linux-vdso.so.1 (0x00007ffc011d2000)
        libdns.so.162 => /lib64/libdns.so.162 (0x00007f042e80e000)
        liblwres.so.141 => /lib64/liblwres.so.141 (0x00007f042e5fa000)
        libbind9.so.140 => /lib64/libbind9.so.140 (0x00007f042e3ea000)
        libisccfg.so.140 => /lib64/libisccfg.so.140 (0x00007f042e1c2000)
        libisccc.so.140 => /lib64/libisccc.so.140 (0x00007f042dfb8000)
        libisc.so.160 => /lib64/libisc.so.160 (0x00007f042dd41000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f042daf3000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f042d80b000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f042d5d8000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f042d3d4000)
        libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f042cf5f000)
        libcap.so.2 => /lib64/libcap.so.2 (0x00007f042cd59000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f042cb3c000)
        libGeoIP.so.1 => /lib64/libGeoIP.so.1 (0x00007f042c90a000)
        libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f042c5a0000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f042c387000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f042c085000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f042be80000)
        libidn.so.11 => /lib64/libidn.so.11 (0x00007f042bc4c000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f042b88b000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f042b67b000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f042b477000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f042b25b000)
        /lib64/ld-linux-x86-64.so.2 (0x00005622f0557000)
        libgomp.so.1 => /lib64/libgomp.so.1 (0x00007f042b039000)
        libattr.so.1 => /lib64/libattr.so.1 (0x00007f042ae32000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f042ac07000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f042a9e3000)
        libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f042a773000)

Comment 1 Tomáš Hozza 2016-04-25 08:52:46 UTC
GeoIP support is a compile time feature. When turned on, it is compiled into bind libraries, which are used by bind itself and also by other tools.

If you have a constructive idea how to do this in a better way, other than once again hack bind and build separate version of libraries and the binary, I don't see any way solution to your request.

Also the situation is an expected outcome of the GeoIP support being turned on.


Note You need to log in before you can comment on or make changes to this bug.