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

30 lines
833 B
Makefile
Raw Normal View History

Import openresolv-3.7.3 with the following changes: * Save the initial working directory and change to it just before running any scripts. This avoids scripts putting files accidently where they shouldn't. * Strip trailing dot from search and domain names. * man page improvements.
2016-02-22 11:11:22 +01:00
# $NetBSD: Makefile,v 1.26 2016/02/22 10:11:22 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
#
Import openresolv-3.7.3 with the following changes: * Save the initial working directory and change to it just before running any scripts. This avoids scripts putting files accidently where they shouldn't. * Strip trailing dot from search and domain names. * man page improvements.
2016-02-22 11:11:22 +01:00
DISTNAME= openresolv-3.7.3
/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/
openresolv-3.7.1 has been released with the following changes: * Typo's, thanks to Herbert Parentes Fortes Neto * Clarify that private_interfaces="*" will not forward the root zone * Change from bzip2 to xz for builiding the source tarball * ensure that domain-insecure always appears in a server clause for the unbound subscriber
2015-09-29 11:19:48 +02:00
EXTRACT_SUFX= .tar.xz
/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
Use roy@NetBSD.org instead of my personal email.
2009-03-17 13:02:34 +01:00
MAINTAINER= roy@NetBSD.org
/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
HOMEPAGE= http://roy.marples.name/projects/openresolv/
COMMENT= Framework for managing /etc/resolv.conf
Use standard location for LICENSE line (in MAINTAINER/HOMEPAGE/COMMENT block). Uncomment some commented out LICENSE lines while here.
2009-05-19 10:59:00 +02:00
LICENSE= modified-bsd
/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
Import openresolv-3.4.0 with the following changes * pdnsd support * Ability to append to the search domains
2010-11-05 10:24:58 +01:00
USE_LANGUAGES= # none
HAS_CONFIGURE= yes
Wire down the 'libexec' directory, to avoid configure making decisions that don't match PLIST. Fixes build on Ubuntu. No change on platforms where the package would successfully build, so no bump required.
2013-06-21 06:46:38 +02:00
CONFIGURE_ARGS+= --libexecdir=${PREFIX}/libexec/resolvconf
Import openresolv-3.4.0 with the following changes * pdnsd support * Ability to append to the search domains
2010-11-05 10:24:58 +01:00
CONFIGURE_ARGS+= --mandir=${PREFIX}/${PKGMANDIR}
CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
Make sure the correct install tool is used.
2012-02-16 20:32:19 +01:00
MAKE_ENV+= INSTALL=${TOOLS_PATH.install:Q}
Update to openresolv-3.0 No functional changes since 2.x, but the configuration has moved from lots of little configuration files into one easier to manage configuration file with a nice man page - resolvconf.conf
2009-03-16 22:55:44 +01:00
EGDIR= ${PREFIX}/share/examples/resolvconf
/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
INSTALL_MAKE_FLAGS+= SYSCONFDIR=${EGDIR}
Update to openresolv-3.0 No functional changes since 2.x, but the configuration has moved from lots of little configuration files into one easier to manage configuration file with a nice man page - resolvconf.conf
2009-03-16 22:55:44 +01:00
CONF_FILES= ${EGDIR}/resolvconf.conf \
${PKG_SYSCONFDIR}/resolvconf.conf
/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-3.0 No functional changes since 2.x, but the configuration has moved from lots of little configuration files into one easier to manage configuration file with a nice man page - resolvconf.conf
2009-03-16 22:55:44 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink