kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/net/openresolv/Makefile

28 lines
769 B
Makefile
Raw Normal View History

Update to openresolv-2.1 No functional changes since 2.0.1 aside from moving the shell scripts out of etc and into libexec. The configuration files in etc/resolvconf/resolv.conf.d have been moved into resolvconf.
2009-03-14 23:33:20 +01:00
# $NetBSD: Makefile,v 1.3 2009/03/14 22:33:20 roy Exp $
/etc/resolv.conf is a file that holds the configuration for the local resolution of domain names. Normally this file is either static or maintained by a local daemon, normally a DHCP daemon. But what happens if more than one thing wants to control the file? Say you have wired and wireless interfaces to different subnets and run a VPN or two on top of that, how do you say which one controls the file? It's also not as easy as just adding and removing the nameservers each client knows about as different clients could add the same nameservers. Enter resolvconf, the middleman between the network configuration services and /etc/resolv.conf. resolvconf itself is just a script that stores, removes and lists a full resolv.conf generated for the interface. It then calls all the helper scripts it knows about so it can configure the real /etc/resolv.conf and optionally any local nameservers other can libc.
2008-12-16 15:57:58 +01:00
#
Update to openresolv-2.1 No functional changes since 2.0.1 aside from moving the shell scripts out of etc and into libexec. The configuration files in etc/resolvconf/resolv.conf.d have been moved into resolvconf.
2009-03-14 23:33:20 +01:00
DISTNAME= openresolv-2.1
/etc/resolv.conf is a file that holds the configuration for the local resolution of domain names. Normally this file is either static or maintained by a local daemon, normally a DHCP daemon. But what happens if more than one thing wants to control the file? Say you have wired and wireless interfaces to different subnets and run a VPN or two on top of that, how do you say which one controls the file? It's also not as easy as just adding and removing the nameservers each client knows about as different clients could add the same nameservers. Enter resolvconf, the middleman between the network configuration services and /etc/resolv.conf. resolvconf itself is just a script that stores, removes and lists a full resolv.conf generated for the interface. It then calls all the helper scripts it knows about so it can configure the real /etc/resolv.conf and optionally any local nameservers other can libc.
2008-12-16 15:57:58 +01:00
CATEGORIES= net
MASTER_SITES= ftp://roy.marples.name/pub/openresolv/
Update to openresolv-2.0.1 Fixes metric support and busybox shell sending dbus to dnsmasq.
2009-02-07 23:57:02 +01:00
MASTER_SITES+= http://roy.aydogan.net/openresolv/
/etc/resolv.conf is a file that holds the configuration for the local resolution of domain names. Normally this file is either static or maintained by a local daemon, normally a DHCP daemon. But what happens if more than one thing wants to control the file? Say you have wired and wireless interfaces to different subnets and run a VPN or two on top of that, how do you say which one controls the file? It's also not as easy as just adding and removing the nameservers each client knows about as different clients could add the same nameservers. Enter resolvconf, the middleman between the network configuration services and /etc/resolv.conf. resolvconf itself is just a script that stores, removes and lists a full resolv.conf generated for the interface. It then calls all the helper scripts it knows about so it can configure the real /etc/resolv.conf and optionally any local nameservers other can libc.
2008-12-16 15:57:58 +01:00
EXTRACT_SUFX= .tar.bz2
MAINTAINER= roy@marples.name
HOMEPAGE= http://roy.marples.name/projects/openresolv/
COMMENT= Framework for managing /etc/resolv.conf
USE_LANGUAGES= # none
PKG_DESTDIR_SUPPORT= user-destdir
PKG_SYSCONFSUBDIR= resolvconf
EGDIR= ${PREFIX}/share/examples/resolvconf
MAKE_ENV+= MANDIR=${PREFIX}/${PKGMANDIR} \
SYSCONFDIR=${PKG_SYSCONFDIR}
INSTALL_MAKE_FLAGS+= SYSCONFDIR=${EGDIR}
OWN_DIRS= ${PKG_SYSCONFDIR}/update.d
Update to openresolv-2.1 No functional changes since 2.0.1 aside from moving the shell scripts out of etc and into libexec. The configuration files in etc/resolvconf/resolv.conf.d have been moved into resolvconf.
2009-03-14 23:33:20 +01:00
CONF_FILES= ${EGDIR}/resolv.conf.head \
${PKG_SYSCONFDIR}/resolv.conf.head
/etc/resolv.conf is a file that holds the configuration for the local resolution of domain names. Normally this file is either static or maintained by a local daemon, normally a DHCP daemon. But what happens if more than one thing wants to control the file? Say you have wired and wireless interfaces to different subnets and run a VPN or two on top of that, how do you say which one controls the file? It's also not as easy as just adding and removing the nameservers each client knows about as different clients could add the same nameservers. Enter resolvconf, the middleman between the network configuration services and /etc/resolv.conf. resolvconf itself is just a script that stores, removes and lists a full resolv.conf generated for the interface. It then calls all the helper scripts it knows about so it can configure the real /etc/resolv.conf and optionally any local nameservers other can libc.
2008-12-16 15:57:58 +01:00
Update to openresolv-2.1 No functional changes since 2.0.1 aside from moving the shell scripts out of etc and into libexec. The configuration files in etc/resolvconf/resolv.conf.d have been moved into resolvconf.
2009-03-14 23:33:20 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink