Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
changes since 2.22 include:
* A bug has been fixed in the tell-position flag. It wasn't actually
giving the file name and line number when executing commands if you
used the "set tell-position" variants, only the -tell-position command
line option.
* A bug has been fixed in the cook -fp-update command, it would
segfault in some cases.
* A bug has been fixed in the cookbook include file processing.
* A bug has been fixed in the negative flag setting (comamnd line
options and "set" clauses).
* The find_command command now copes better with directories it is not
allowed to access.
* A Java cookbook has been added to to the distribution.
* A bug has been fixed in the execution of some commands. If any words
of the command had spaces in them, it did not pass it to a shell to be
executed, but instead constructed a command of a different shape than
the user expected.
* A bug has been fixed on Linux (and it only ever ocurred on Linux)
where cook would suddenly stop for no reason with exit status 1. Turns
out that sometimes fflush(stderr) returns an EAGAIN error.
* A bug has been fixed which caused the cook -script option to produce
invalid shell scripts when a recipe body contained no statements.
* A bug has been fixed in the graph file pair generation, used to
generate warnings about dangerous #include-cooked contents.
* There is a new tell-position setting, so that when Cook prints a
command it is about to run, it includes the file name and line nunmber
of the command. This can be useful when debugging cookbooks.
* A bug has been fixed in the output line wrapping. Once again it
adapts to the window width.
* A major problem with parallel execution and hangs has been fixed.
The table indexed by process ID was now growing correctly.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
* A small problem with fingerprints has been fixed.
* A tutorial has been contributed.
* You can now have international characters in comments.
* A C++ cookbook has been added.
* A test failure on Cygwin has been fixed.
* The [read] and [read_lines] builtin functions have been
added. See the Reference Manual for more information.
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
Cook is a tool for constructing files. It is given a set of files to create,
and recipes of how to create them. In any non-trivial program there will be
prerequisites to performing the actions necessary to creating any file, such
as include files. Cook provides a mechanism to define these.
