INSTALL/DEINSTALL script creation within pkgsrc.
If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts. If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:
INSTALL_SRC= ${PKGDIR}/INSTALL
DEINSTALL_SRC= # emtpy
As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts. By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).
In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework. The only public variables relating to the templates are:
INSTALL_SRC INSTALL_TEMPLATE
DEINSTALL_SRC DEINSTALL_TEMPLATE
HEADER_TEMPLATE
The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
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.
3.6.6
- support for olitec-SX200
- added sample-etc_rc.d_init.d_ddclient.lsb as a sample script for lsb-compliant systems.
- support for linksys wrt854g (thanks to Nick Triantos)
- support for linksys ver 3
- support for Thomson (Alcatel) SpeedTouch 510 (thanks to Aldoir)
- Cosmetic fixes submitted by John Owens
3.6.5
- there was a bug in the linksys-ver2
- support for postscript (thanks to Larry Hendrickson)
- Changelog out of README
- modified all documentation to use /etc/ddclient/ddclient.conf (notified by nicolasmartin in bug [1070646])
3.6.4
- added support for NameCheap service (thanks to Dan Boardman)
- added support for linksys ver2 (thanks to Dan Perik)
3.6.3
- renamed sample-etc_dhclient-enter-hooks to sample-etc_dhclient-exit-hooks
- add support for the Allnet 1298 Router
- add -a to ifconfig to query all interfaces (for Solaris and OpenBSD)
- update the process status to reflect what is happening.
- add a To: line when sending e-mail
- add mail-failure to send mail on failures only
- try all addresses for multihomed hosts (like check.dyndns.org)
- add support for dnspark
- add sample for OrgDNS.org
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.
This is from ideas from Greg Woods and others.
Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
the RCD_SCRIPTS rc.d script(s) to the PLIST.
This GENERATE_PLIST idea is part of Greg A. Woods'
PR #22954.
This helps when the RC_SCRIPTS are installed to
a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later,
the default RCD_SCRIPTS_EXAMPLEDIR will be changed
to be more clear that they are the examples.)
These patches also remove the etc/rc.d/ scripts from PLISTs
(of packages that use RCD_SCRIPTS). (This also removes
now unused references from openssh* makefiles. Note that
qmail package has not been changed yet.)
I have been doing automatic PLIST registration for RC_SCRIPTS
for over a year. Not all of these packages have been tested,
but many have been tested and used.
Somethings maybe to do:
- a few packages still manually install the rc.d scripts to
hard-coded etc/rc.d. These need to be fixed.
- maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
USE_PKGINSTALL is "YES". bsd.pkg.install.mk will no longer automatically
pick up a INSTALL/DEINSTALL script in the package directory and assume that
you want it for the corresponding *_EXTRA_TMPL variable.
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
- add support for Xsense Aero
- add support for Alcatel Speedtouch Pro
- do authentication when either the login or password are defined.
- fix parsing of web status pages
Updated contributed by Amitai Schlair <schmonz@schmonz.com> in private mail.
- buildlink'ify
- use general INSTALL scripts as ddclient now requires a config file and
can use a rc.d script to operate in daemon mode
Changes from version 2.3.2 include:
- bug fixes
- new ddclient.conf format
- rewritten to support DynDNS's NIC2 and other dynamic DNS services:
- added EasyDNS (easydns.com)
- added Hammernode (hn.org)
- added ZoneEdit (zoneedit.com)
- added DSLreports (dslreports.com) host monitoring
- added support for obtaining IP addresses from :
- interfaces, commands, web, external commands, routers
- added daemon mode
- added logging msgs to syslog and e-mail
- add detection of SIGHUP. When this signal is received, ddclient will
wake up immediately, reload it's configuration file, and update
the IP addresses if necessary.
Convert most MESSAGE files to new syntax (${VARIABLE} gets replaced,
not @VARIABLE@, nor @@VARIABLE@@).
By default, substitutions are done for LOCALBASE, PKGNAME, PREFIX,
X11BASE, X11PREFIX; additional patterns can be added via MESSAGE_SUBST.
Clean up some packages while I'm there; add RCS tags to most MESSAGEs.
Remove some uninteresting MESSAGEs.
on Dynamic DNS Network Services' free DNS service. See http://www.dyndns.org
for details on obtaining a free account.
Comments can always be sent to:
mailto:paul+ddclient@burry.dyndns.org
If you use ddclient, please send a brief note to:
mailto:paul+ddclient@burry.dyndns.org
and indicate if you would like to be notified of new releases.
