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

45 lines
1.1 KiB
Makefile
Raw Normal View History

all: migrate homepages from http to https pkglint -r --network --only "migrate" As a side-effect of migrating the homepages, pkglint also fixed a few indentations in unrelated lines. These and the new homepages have been checked manually.
2020-01-26 18:30:40 +01:00
# $NetBSD: Makefile,v 1.22 2020/01/26 17:31:49 rillig Exp $
Import dhisd-5.0: DynDNS server By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.
2001-06-06 01:39:27 +02:00
#
(pkgsrc/Makefile) - Add LICENSE= 2-clause-bsd - Drop PKG_DESTDIR_SUPPORT= - Add SUBST_CLASSES to edit Makefile for PREFIX - Add SUBST_CLASSES to edit dhisd.h and README for VARVASE and PREFIX - Add SPECIAL_PERMS to set mode 0700 owner root onto executables (pkgsrc/DESCR) - Add pointer to ${PREFIX}/share/doc/dhisd/README for info (pkgsrc/patches/patch-aa) - Removed (upstream) - Update 5.1 to 5.5 ----------------- On dhisd-5.5 The server no longer requires a 5.4 client to have rport=0 in order to reply to the sending port. This releases a small issue that broke 5.4 clients with servers <= 5.3. As of this version, if the client's version is 5.4 or higher, the server always replies to the sending UDP port and disregards rport. 5.5. clients however continue to fill in rport in order to be compatible with <= 5.3 servers. On dhisd-5.4: The modular architecture has been dropped and the modules and engines are no longer part of dhisd. Instead dhisd is again a DNS only updating daemon without engines; the extra functionality provided by previous engines can however still be replicated with OnCmd and OffCmd scripts on a per-host basis. The default configuration directory is now /usr/local/etc The default binaries directory is now /usr/local/sbin It is now possible to put all configuration parameters under a config file; the default is /usr/local/etc/dhisd.conf The pid file default location moved to /var/run/dhis/dhisd.pid The log file default location moved to /var/log/dhis/dhisd.log The server can now be bound to a specific IP address with either the BindAddr config option or the -b command line option. Multiple options have been added and are now possible with the command line (dhisd -h) and the config file. The server now binds to a UDP port (58800 by default) and sends UDP messages from that port; in previous versions dhisd sent UDP messages from a random port even though it listened on port 58000. In addition to the database text file (specified by the -d option or the DBFile config option), dhisd can now use a MySQL database instead to achieve the same purpose of the dhis.db file. See README and INSTALL for details. This version of the server is compatible with NAT friendly 5.4 clients. On dhisd-5.3: Corrected bug that caused improper handling of comment character (;) in the database file. On dhisd-5.2: Documentation Updates
2015-03-08 02:01:52 +01:00
DISTNAME= dhisd-5.5
Import dhisd-5.0: DynDNS server By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.
2001-06-06 01:39:27 +02:00
CATEGORIES= net
MASTER_SITES= ftp://ftp.dhis.org/pub/dhis/
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
all: migrate homepages from http to https pkglint -r --network --only "migrate" As a side-effect of migrating the homepages, pkglint also fixed a few indentations in unrelated lines. These and the new homepages have been checked manually.
2020-01-26 18:30:40 +01:00
HOMEPAGE= https://www.dhis.org/
Import dhisd-5.0: DynDNS server By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.
2001-06-06 01:39:27 +02:00
COMMENT= DynDNS server
(pkgsrc/Makefile) - Add LICENSE= 2-clause-bsd - Drop PKG_DESTDIR_SUPPORT= - Add SUBST_CLASSES to edit Makefile for PREFIX - Add SUBST_CLASSES to edit dhisd.h and README for VARVASE and PREFIX - Add SPECIAL_PERMS to set mode 0700 owner root onto executables (pkgsrc/DESCR) - Add pointer to ${PREFIX}/share/doc/dhisd/README for info (pkgsrc/patches/patch-aa) - Removed (upstream) - Update 5.1 to 5.5 ----------------- On dhisd-5.5 The server no longer requires a 5.4 client to have rport=0 in order to reply to the sending port. This releases a small issue that broke 5.4 clients with servers <= 5.3. As of this version, if the client's version is 5.4 or higher, the server always replies to the sending UDP port and disregards rport. 5.5. clients however continue to fill in rport in order to be compatible with <= 5.3 servers. On dhisd-5.4: The modular architecture has been dropped and the modules and engines are no longer part of dhisd. Instead dhisd is again a DNS only updating daemon without engines; the extra functionality provided by previous engines can however still be replicated with OnCmd and OffCmd scripts on a per-host basis. The default configuration directory is now /usr/local/etc The default binaries directory is now /usr/local/sbin It is now possible to put all configuration parameters under a config file; the default is /usr/local/etc/dhisd.conf The pid file default location moved to /var/run/dhis/dhisd.pid The log file default location moved to /var/log/dhis/dhisd.log The server can now be bound to a specific IP address with either the BindAddr config option or the -b command line option. Multiple options have been added and are now possible with the command line (dhisd -h) and the config file. The server now binds to a UDP port (58800 by default) and sends UDP messages from that port; in previous versions dhisd sent UDP messages from a random port even though it listened on port 58000. In addition to the database text file (specified by the -d option or the DBFile config option), dhisd can now use a MySQL database instead to achieve the same purpose of the dhis.db file. See README and INSTALL for details. This version of the server is compatible with NAT friendly 5.4 clients. On dhisd-5.3: Corrected bug that caused improper handling of comment character (;) in the database file. On dhisd-5.2: Documentation Updates
2015-03-08 02:01:52 +01:00
LICENSE= 2-clause-bsd
Import dhisd-5.0: DynDNS server By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.
2001-06-06 01:39:27 +02:00
SunOS needs -lsocket -lnsl.
2014-09-23 19:57:04 +02:00
LDFLAGS.SunOS+= -lsocket -lnsl
PKG_DESTDIR_SUPPORT
2009-12-18 01:39:50 +01:00
INSTALLATION_DIRS= bin share/examples/dhisd share/doc/dhisd
(pkgsrc/Makefile) - Add LICENSE= 2-clause-bsd - Drop PKG_DESTDIR_SUPPORT= - Add SUBST_CLASSES to edit Makefile for PREFIX - Add SUBST_CLASSES to edit dhisd.h and README for VARVASE and PREFIX - Add SPECIAL_PERMS to set mode 0700 owner root onto executables (pkgsrc/DESCR) - Add pointer to ${PREFIX}/share/doc/dhisd/README for info (pkgsrc/patches/patch-aa) - Removed (upstream) - Update 5.1 to 5.5 ----------------- On dhisd-5.5 The server no longer requires a 5.4 client to have rport=0 in order to reply to the sending port. This releases a small issue that broke 5.4 clients with servers <= 5.3. As of this version, if the client's version is 5.4 or higher, the server always replies to the sending UDP port and disregards rport. 5.5. clients however continue to fill in rport in order to be compatible with <= 5.3 servers. On dhisd-5.4: The modular architecture has been dropped and the modules and engines are no longer part of dhisd. Instead dhisd is again a DNS only updating daemon without engines; the extra functionality provided by previous engines can however still be replicated with OnCmd and OffCmd scripts on a per-host basis. The default configuration directory is now /usr/local/etc The default binaries directory is now /usr/local/sbin It is now possible to put all configuration parameters under a config file; the default is /usr/local/etc/dhisd.conf The pid file default location moved to /var/run/dhis/dhisd.pid The log file default location moved to /var/log/dhis/dhisd.log The server can now be bound to a specific IP address with either the BindAddr config option or the -b command line option. Multiple options have been added and are now possible with the command line (dhisd -h) and the config file. The server now binds to a UDP port (58800 by default) and sends UDP messages from that port; in previous versions dhisd sent UDP messages from a random port even though it listened on port 58000. In addition to the database text file (specified by the -d option or the DBFile config option), dhisd can now use a MySQL database instead to achieve the same purpose of the dhis.db file. See README and INSTALL for details. This version of the server is compatible with NAT friendly 5.4 clients. On dhisd-5.3: Corrected bug that caused improper handling of comment character (;) in the database file. On dhisd-5.2: Documentation Updates
2015-03-08 02:01:52 +01:00
SUBST_CLASSES+= varbase
SUBST_FILES.varbase= dhisd.h README
SUBST_STAGE.varbase= pre-configure
SUBST_MESSAGE.varbase= Adapt VARBASE and PREFIX
SUBST_VARS.varbase+= VARBASE PREFIX
net: align variable assignments pkglint -Wall -F --only aligned --only indent -r No manual corrections.
2019-11-03 12:45:28 +01:00
SPECIAL_PERMS+= bin/dhisd-genkeys ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700 \
bin/dhisd ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
Import dhisd-5.0: DynDNS server By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.
2001-06-06 01:39:27 +02:00
do-install:
net: align variable assignments pkglint -Wall -F --only aligned --only indent -r No manual corrections.
2019-11-03 12:45:28 +01:00
${INSTALL_DATA} \
${WRKSRC}/*.sample \
${DESTDIR}${PREFIX}/share/examples/dhisd
${INSTALL_DATA} \
${WRKSRC}/CONTRIBUTORS \
${WRKSRC}/COPYRIGHT \
${WRKSRC}/INSTALL \
${WRKSRC}/README \
${DESTDIR}${PREFIX}/share/doc/dhisd
${INSTALL_PROGRAM} \
${WRKSRC}/dhisd \
${DESTDIR}${PREFIX}/bin
${INSTALL_PROGRAM} \
${WRKSRC}/dhisgenkeys \
${DESTDIR}${PREFIX}/bin/dhisd-genkeys
Import dhisd-5.0: DynDNS server By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.
2001-06-06 01:39:27 +02:00
Convert to buildlink3 and correct two spelling errors in DESCR.
2004-04-25 10:59:48 +02:00
.include "../../devel/gmp/buildlink3.mk"
Import dhisd-5.0: DynDNS server By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.
2001-06-06 01:39:27 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink