1 Summary: A POSIX resolvconf(8) implementation, a middleman for resolv.conf(5)
7 Source0: https://roy.marples.name/downloads/openresolv/%{name}-%{version}.tar.xz
8 # Source0-md5: 595f8633c111c150b86825b027e0bbde
9 URL: https://roy.marples.name/projects/openresolv/
12 BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n)
15 /etc/resolv.conf is a file that holds the configuration for the local
16 resolution of domain names. Normally this file is either static or
17 maintained by a local daemon, normally a DHCP daemon. But what happens
18 if more than one thing wants to control the file? Say you have wired
19 and wireless interfaces to different subnets and run a VPN or two on
20 top of that, how do you say which one controls the file? It’s also not
21 as easy as just adding and removing the nameservers each client knows
22 about as different clients could add the same nameservers.
24 Enter resolvconf, the middleman between the network configuration
25 services and /etc/resolv.conf. resolvconf itself is just a script that
26 stores, removes and lists a full resolv.conf generated for the
27 interface. It then calls all the helper scripts it knows about so it
28 can configure the real /etc/resolv.conf and optionally any local
29 nameservers other than libc.
36 --libexecdir=%{_libexecdir}/%{name} \
41 rm -rf $RPM_BUILD_ROOT
44 DESTDIR=$RPM_BUILD_ROOT
47 rm -rf $RPM_BUILD_ROOT
50 %defattr(644,root,root,755)
52 %config(noreplace,missingok) %verify(not md5 mtime size) %{_sysconfdir}/resolvconf.conf
53 %attr(755,root,root) /sbin/resolvconf
54 %dir %{_libexecdir}/%{name}
55 %{_libexecdir}/%{name}/dnsmasq
56 %{_libexecdir}/%{name}/libc
57 %dir %{_libexecdir}/%{name}/libc.d
58 %{_libexecdir}/%{name}/libc.d/avahi-daemon
59 %{_libexecdir}/%{name}/libc.d/mdnsd
60 %{_libexecdir}/%{name}/named
61 %{_libexecdir}/%{name}/pdns_recursor
62 %{_libexecdir}/%{name}/pdnsd
63 %{_libexecdir}/%{name}/unbound
64 %{_mandir}/man5/resolvconf.conf.5*
65 %{_mandir}/man8/resolvconf.8*