0.09 2014-10-05
- Clarify which of List::Util and List::MoreUtils wins when they both provide
the same function. Requested by Karen Etheridge. RT #98560.
the previous version. However, there are now tests (which pass), and
I've been running this version since June.
New in Version 0.9.1, released 2014-06-09
* When installing a new config file, create the config file's parent
directories if they don't exist. If a directory is created, the
permissions and ownership are copied from the corresponding
directory in the upstream config file hierarchy.
* Add a new --version (-V) option.
* Add a new --help (-h) option.
* etcmanage now exits with an error if an unsupported argument is
specified.
* 'etcmanage --remove' no longer warns if the given file was not
already in the database.
New in Version 0.9, released 2014-05-21
* Use Perl's Digest::MD5 module instead of the md5 utility for
compatibility with other operating systems.
* Add a new --destdir option. If specified, the filenames for all
operations will be prefixed with the provided directory name.
This makes it possible to use etcmanage on a chroot or DESTDIR
environment.
* Don't automatically update the hash stored in the database if a
live config file is modified and upstream is changed to match.
This matches the behavior when both the live file and upstream
file have been deleted (the record isn't removed from the
database) and it provides an important invariant: If the state of
the live config file does not match the state of the database
record, nothing is modified.
* Fix handling of removed files during 'etcmanage --update': If a
managed file is deleted, treat it as a manual modification---don't
restore the upstream file.
* Improve logging:
- Log problems updating config files to standard error (STDERR)
instead of standard output (STDOUT).
- During 'etcmanage --update', log "UNMANAGED_EQ_UPSTREAM" when
encoutering a new upstream file that is already installed with
identical contents.
- During 'etcmanage --update', log "UNMANAGED_NEQ_UPSTREAM" to
STDERR when encoutering a new upstream file that is already
installed but has different contents.
- Log three distinct types of "MISSING" messages instead of one:
* "MISSING" is logged when the hash of the upstream file matches
the database entry
* "MISSING;UPSTREAM_WITHDRAWN" is logged when the upstream file
doesn't exist
* "MISSING;UPSTREAM_DIFFERENT" is logged when the hash of the
upstream file differs from the hash stored in the database
- Use the term "MODIFIED" instead of "CONFLICT" and split it into
three distinct types of "MODIFIED" messages instead of one:
* "MODIFIED" is logged when the hash of the upstream file
matches the database entry
* "MODIFIED;UPSTREAM_WITHDRAWN" is logged when the upstream file
doesn't exist
* "MODIFIED;UPSTREAM_DIFFERENT" is logged when the hash of the
upstream file differs from the hash stored in the database
* During 'etcmanage --update <dir>', visit all files in '<dir>', not
just '<dir>/etc'. This makes it possible to use etcmanage to
manage files outside of '/etc', but is unfortunately not
backwards-compatible: 'etcmanage --update' can no longer be
pointed to a DESTDIR containing a complete NetBSD build (or else
all operating system files---not just config files---will be
managed by etcmanage).
* During 'etcmanage --generate-manifest <dir>', visit all files in
'<dir>', not just '<dir>/etc'. This makes it easier to use
etcmanage to manage files outside of '/etc', but is unfortunately
not backwards-compatible: 'etcmanage --generate-manifest' can no
longer be pointed to a DESTDIR containing a complete NetBSD build
(or else all operating system files---not just config files---will
be included in the manifest).
* Add support for systems that don't have an /etc/services file or
don't consider the /etc/services file to be a configuration file.
* Fix command line parsing. It is now possible to specify multiple
commands at once (including repeating a command) and they will be
executed in the specified order.
* Add a '--db' option to specify the database filename.
* Add a new '--manual' command to mark a file as manually managed.
This differs from '--remove' in that a future '--update' will
never automatically cause the file to become managed. It also
results in different log messages being printed when a config file
has been modified, and these log messages are printed to STDOUT
instead of STDERR (because they are expected conditions).
* Refuse to add abnormal pathnames to the database. A pathname is
considered abnormal if it has any of the following properties:
- contains whitespace
- begins with '#'
- is the empty string
- is relative
- contains '/../', '/./', or superfluous slashes
Pathnames with the first three properties in the above list cannot
be represented in a manifest. Relative pathnames do not make
sense (what are they relative to?). Pathnames with '/../', '/./',
or superfluous slashes can result in unintentional duplicate
database entries that conflict with each other.
* Various code cleanups.
* Various build system improvements.
- Add cdio_free, iso9660_stat_free, and iso9660_xa_free functions.
- Deprecate mmc_isrc_track_read_subchannel
- Add mmc_get_track_isrc function.
- Update OS versions we recognize
- OSX, and MS Windows, ISO 9660 and other bug fixes
- Remove Coverty scan warnins and errors
- OS/2 driver performance update
- Provisional Django 1.7 support
- Multi-db and multi-manager support to management commands
- Added index on reversion.date_created
- Minor bugfixes and documentation improvements
=================
WebKitGTK+ 2.4.6
=================
What's new in WebKitGTK+ 2.4.6?
- Use free icons for the web inspector.
- Make vimeo videos work again with the GStreamer media backend.
- Fix selection rendering when unfocused with recent GTK+ versions.
- Fix toggle buttons rendering with recent GTK+ versions.
- Fix race condition when downloading a file due to the intermediate
temporary file.
- 2.38 | 2014-10-08
- bug-report address changed
Please send bug reports to the address shown by running command:
./configure --help
Mail sent to the previous address is likely to be misplaced.
- bugfixes
- ‘parse-form’ uses ‘list’ instead of ‘values’
NB: Backward-incompatible change.
Previously, this ‘(www server-utils form-2-form)’ proc would use
‘values’ for form elements that have type info, consing the
result into the returned alist. Unfortunately, use of ‘values’
outside a ‘call-with-values’ context (e.g., as a container, as
in this case) is not supported by Guile 2.x.
Now, the four pieces of type info are packaged w/ ‘list’.
- support for VPATH "make check"
Previously VPATH "make check" failed to initialize each test's
infrastructure (i.e., v/common). Now it takes into account the
configure-substituted and Makefile var ‘srcdir’ as well.
- new optional arg ‘u8’
- ‘(www url-coding) url-coding:decode’
This proc now takes an optional arg U8, which if non-‘#f’, means
to return a u8vector instead of a string.
- ‘(www server-utils parse-request) alist<-query’
This proc now takes an optionl arg U8, which if non-‘#f’, means
to return u8vectors instead of strings for names and values.
- changes to ‘(www server-utils form-2-form) parse-form’
- non-string args ok
The first arg can now be a form:
((multipart . MINOR) PARAMETER...)
i.e., the parsed form of the Content-Type header's value.
Relatedly, the arg's documented name is now simply TYPE.
The second arg can now be an integer specifying the number of
bytes to read from the current input port.
For backward compatibility, TYPE and RAW-DATA can also be
strings.
- sub ‘multipart/mixed’ better recognized
Previously, a (sub) part w/ "Content-Type: multiPART / miXed"
(for instance) would be handled opaquely. Now, such a header is
properly recognized and recursed into. Sigh, one has to wonder:
Will there ever be a more tightly specified MIME 2.0?
- CGI file-uploads can now be done in "move u8" style
Proc ‘(www cgi) cgi:init’ now accepts options ‘move’, which
controls how file-uploads are handled. When specified, the
uploaded files are returned as procedures that can be called to
write the actual contents of the file (a u8vector) to a port or
to return those contents directly. This option takes precedence
over ‘uploads-lazy’.
Another new option is ‘move-simple-text/plain’, which only is
meaningful if ‘move’ is also specified. This simplifies the
value of form parameters with MIME type ‘text/plain’ to a
string, discarding other MIME information.
See examples/id.cgi.in for how to use these options.
- "make check" locale support
You can customize (somewhat) the locale that tests use by
manipulating file v/testing-locale. See README.
- bootstrap tools upgraded
- GNU Automake 1.14.1
- Guile-BAUX 20140110.0849.39e9660
