Am 27.09.2016 um 21:32 schrieb Roman Tsisyk:
Hi, My package uses getprotobyname(3), getaddrinfo(3), getnameinfo(3) functions which read /etc/protocols, /etc/hosts, /etc/services and other network configuration files under the hood. Despite the fact that all these functions is an integral part of glibc, required configuration files are provided by a separate package called `setup`, which is not in the dependency tree of glibc. I realized that it is possible break getprotoname(2), getaddrinfo(2), getnameinfo(2) and probably other glibc functions by removing `setup` package. Moreover, some authors of Docker containers already do that to minimize image footprint. Is it a dependency problem of glibc package? Should I file a ticket for this case? Is it better to add /etc/protocols, /etc/services or `setup` as dependencies for my package?
I'd file a bug on glibc and add a dependency on those files (or the package shipping them) in your package at least as long until the issue is resolved by the glibc-maintainers.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
