* Consolidate lines that end in a '\' followed by an empty line into one
newline prior to splitting the Makefile into sections. This will more
properly catch section-related errors [1]
* Properly check pkg-config files when they contain an embedded '.' [2]
* Allow pkg-plist directive @cwd by itself which means to change the working
directory back to the original PREFIX [3]
* Beef up the warnings around DOCSDIR, EXAMPLESDIR, and DATADIR so that
users don't just use these macros without knowing if they are safe [3]
* Check for use of --mandir and --infodir [4]
PR: 112332 [1]
115455 [4]
Submitted by: rafan [4]
sat [2]
Requested by: pav [3]
In short, it was dropping privs before setting PID. Patch the code locally to
get FreeBSD users running.
- While here, if PostgreSQL is not installed, ask for 8.2, not the default of
8.1.
- Remove EOT model patch, now in vendor code.
- Update pkg-message to reflect new version.
PR: 115582
Submitted by: Dan Langille (maintainer)
- Bump PORTREVISION
- Schedule for expiration on 2007-11-16
USE_X_PREFIX is not neccesary (these are script-only ports) and it is
removed to reduce build times on clusters.
Ports depending on tkstep80 are very old (~1999), not developed and
unmaintained.
GNU ddrescue is a data recovery tool. It copies data from one file or
block device (hard disc, cdrom, etc) to another, trying hard to rescue
data in case of read errors. Ddrescue does not truncate the output file
if not asked to. So, every time you run it on the same output file, it
tries to fill in the gaps. The basic operation of ddrescue is fully
automatic. That is, you don't have to wait for an error, stop the
program, read the log, run it in reverse mode, etc. If you use the
logfile feature of ddrescue, the data is rescued very efficiently (only
the needed blocks are read). Also you can interrupt the rescue at any
time and resume it later at the same point.
Automatic merging of backups: If you have two or more damaged copies of
a file, cdrom, etc, and run ddrescue on all of them, one at a time,
with the same output file, you will probably obtain a complete and
error-free file. This is so because the probability of having damaged
areas at the same places on different input files is very low. Using
the logfile, only the needed blocks are read from the second and
successive copies.
WWW: http://www.gnu.org/software/ddrescue/ddrescue.html
Author: Antonio Diaz Diaz <ant_diaz@teleline.es>
