… DESTDIR=/tmp/pacage install"
…ons. Include Peter Eisentraut's script to re-add implicit casts to PostgreSQL 8.3, as his Planet PostgreSQL blog is no longer available.
… use old compatible numbering.
… that no one uses any more.
* Added GPL and copyright headers to a few files that were missing them.
install IC. * Put 'require 5.6.0' in Makefile.PL to set the minimum Perl version.
* Default is no change, i.e. no cron. * The recommended method to add the file is: HouseKeepingCron <crontab That will use the file etc/lib/crontab by default in the tarball, or /etc/interchangec/crontab in an LSB configuration. * Requires the Set::Crontab module, which has been added to Bundle::Interchange. * Structure of the crontab file is just like crontab(5) in UNIX except that a seconds column is added. The targets are GlobalSub or anything which you can make run with Vend::Dispatch::run_macro. Bear in mind there is no catalog context. Two special targets exist, :reconfig and :jobs. They allow calling of the catalog reconfig routines and jobs routines, respectively. The etc/reconfig and etc/jobsqueue files will be ignored if these targets are not present -- a warning will be issued at startup (and crontab change) if they are not there. A target prepended with > runs *after* the reconfig/restart/jobs/pid mgmt cycle. Normal specifications run before. The basic entry to implement "HouseKeeping 5" would be: HouseKeeping 1 HouseKeepingCron <<EOC */5 * * * * * :restart */5 * * * * * :jobs EOC (Note that would normally be in etc/lib/crontab or /etc/interchange/crontab.) To only check the jobs queue every five minutes (on the minute), you do: */5 * * * * * :restart 0 */5 * * * * :jobs If you want to run the GlobalSub "checkit" once a day at 4am, you would do: 0 0 4 * * * checkit * If you set HouseKeeping to a granularity besides 1 (or if for some reason Interchange skips a second), it does the cron check for every intervening second. This ensures a job will not be skipped. The :restart and :jobs entries will only run once, but if you have a frequent GlobalSub job that pushes the granularity of HouseKeeping it can be run twice in succession. * WARNING: You should not put long-running jobs in a GlobalSub! You have been warned. Use the Jobs facility for that. * Probably should implement the ability to call out jobs, but not quite sure how to specify and do. Can we just call run_jobs() directly? If so, then maybe an = sign introduces a job: 0 0 * * * * =standard_cat hourly 0 0 4 * * * =standard_cat daily 0 0 2 * * 7 =standard_cat weekly * Include bin/crontab script to edit the crontab and submit to the running IC daemon. BUG: Cannot run as root.
manual installation. 1. Query on installation with a threaded Perl. If you answer "yes" it will create the file _allow_threads and then build and test. 2. Added an os hint that inserts the MV_GETPPID_BROKEN fix if on Linux and running threads. 3. Once you have installed with threads, and the _allow_threads file is in the IC root, you don't need to set the environment variable anymore. You will get a warning. 4. Put in a check for Perl 5.8.5 to be allowed to run with threads. There were several ithreads bugs fixed in that version.
…ames back on track). Start using version-specific WHATSNEW file so we can keep old ones around. They're important documentation for the project but it's too hard to find old ones without downloading old code.
copyright year in other files as we make changes to them.