| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
* prevent to pick up swig2
Bump PKGREVISION.
|
|
|
|
Noteworthy changes in version 1.0.0 (2012-08-27)
------------------------------------------------
* Make sure to create parent directory of user-dict (Debian bug#685745).
* Clear output and preedit on context reset.
* Fix header include in tests (Issue#19).
|
|
|
|
|
|
Fixes and changes after 2.16.0
==============================
2.16.1
Please refer to the bug tracker for issues fixed in 2.16.1
(http://code.google.com/p/lilypond/issues/list?can=1&q=Fixed_2_16_1).
New features in 2.16 since 2.14
===============================
* Support for cross-staff stems on chords, using `crossStaff' and
the `Span_stem_engraver'. This calculates the length of
cross-staff stems automatically.
* The syntax of words (character sequences recognized without
enclosing quotes) and commands (now always a backslash `\'
followed by a word) has been unified across all modes: it now
consists of alphabetic characters, possibly enclosing isolated
dashes `-' and underlines `_'.
As one consequence, using unquoted text scripts like (literally!)
{ c-script c\f_script }
will now tend to result in invalid music. Omitting quote marks
for arbitrary text rather than keywords has never been good
practice or even documented, and it is unlikely to have seen
significant use.
Staying with established conventions (like not using dashes or
underlines for command names intended to be used inside of music)
remains advisable. The reason for this change is more robust
recognition of LilyPond's lexical units for LilyPond itself as
well as external tools interpreting its syntax.
* Support for Kievan square notation:
\new KievanVoice {
\cadenzaOn
c d e f g a bes
\bar "kievan"
}
* Augmentation dots now avoid the other voice in two-voice polyphony
so that users can move the `Dot_column_engraver' to set dots
independently for each `Voice'.
* A Scheme function to adjust the control points of curves such as
slurs and ties, developed by several users, is now included in
LilyPond.
g8->( bes,-.) d4
\shape Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0))
g8->( bes,!-.) d4
* Use of `\tempo' specifications in `\midi' blocks (removed in
2.9.16 in favor of explicit `tempoWholesPerMinute' settings) has
seen a revival: now any kind of property-setting music is turned
into context definitions within output specifications, allowing for
declarations like
\layout { \accidentalStyle modern }
\midi { \tempo 4. = 66 }
* The LilyPond G clef has been redesigned - upper loop is now more
balanced, bottom crook sticks out less and the "spine" (main
vertical line) is more evenly curved. The old and new versions can
be compared by looking at the documentation: old version
(http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs),
new version
(http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs).
* Lilypond's stencil commands have been simplified to allow for less
code duplication and better height approximations of graphical
objects. The following stencil commands have been eliminated:
* `beam'
* `bezier-sandwich'
* `bracket'
* `dashed-slur'
* `dot'
* `oval'
* `repeat-slash'
* `zigzag-line'
* Flags are now treated as separate objects rather than as stem
parts.
* Two alternative methods for bar numbering can be set, especially
for when using repeated music;
* The following is a fundamental change in LilyPond's music
representation: Rhythmic events like `LyricEvent' and `NoteEvent'
are no longer wrapped in `EventChord' unless they have been
actually entered as part of a chord in the input. If you
manipulate music expressions in Scheme, the new behavior may
require changes in your code. Calling the music function
`\eventChords' or the Scheme function `event-chord-wrap!'
converts to the old representation; using one of those might be
easiest for keeping legacy code operative.
The following three items are consequences of this change.
* The repetitive chord entry aid `q' has been reimplemented.
Repeated chords are now replaced right before interpreting a music
expression. In case the user wants to retain some events of the
original chord, he can run the repeat chord replacement function
`\chordRepeats' manually.
* String numbers and right hand fingerings on single notes now appear
without having to be written inside of chord brackets.
* Music functions now work the same when used inside or outside of
chords, including all the possibilities of argument parsing.
Music variables can be used inside of chords: a construct like
tonic=fis'
{ <\tonic \transpose c g \tonic> }
now works as expected. One can use `#{...#}' for constructing
chord constituents. `\tweak' now works on single notes without
needing to wrap them in a chord. Using it on command events and
lyrics is now possible, but not likely to give results yet.
* `\tweak' now takes an optional layout object specification. It can
be used for tweaking layout objects that are only indirectly
caused by the tweaked event, like accidentals, stems, and flags:
<\tweak Accidental #'color #red cis4
\tweak Accidental #'color #green es
g>
* Scheme expressions inside of embedded Lilypond (`#{...#}') are now
executed in lexical closure of the surrounding Scheme code. `$'
is no longer special in embedded Lilypond. It can be used
unconditionally in Lilypond code for immediate evaluation of Scheme
expressions, similar to how `ly:export' could previously be used.
`ly:export' has been removed. As a consequence, `#' is now free
to delay evaluation of its argument until the parser actually
reduces the containing expression, greatly reducing the potential
for premature evaluation. There are also `splicing' operators `$@'
and `#@' for interpreting the members of a list individually.
* To reduce the necessity for using `$', Scheme expressions written
with `#' are interpreted as music inside of music lists, and as
markups or markup lists inside of markups.
* Support for jazz-like chords has been improved: Lydian and altered
chords are recognised; separators between chord modifiers are now
treated independently of separators between "slash" chords and
their bass notes (and by default, slashes are now only used for
the latter type of separator); additional pitches are no longer
prefixed with "add" by default; and the "m" in minor chords can be
customized. *note Customizing chord names:
(lilypond-notation)Customizing chord names. for more information.
* The `\markuplines' command has been renamed to `\markuplist' for a
better match with its semantics and general Lilypond nomenclature.
* The interface for specifying string tunings in tablature has been
simplified considerably and employs the scheme function
`\stringTuning' for most purposes.
* Beams can now have their slopes preserved over line breaks.
To do this, several callback functions are now deprecated.
* `ly:beam::calc-least-squares-positions'
* `ly:beam::slope-damping'
* `ly:beam::shift-region-to-valid'
Furthermore, `ly:beam::quanting' now takes an additional argument
to help calculations over line breaks. All of these functions are
now automatically called when setting the `positions' parameter.
* In function arguments music, markups and Scheme expressions (as
well as several other syntactic entities) have become mostly
interchangeable and are told apart only by evaluating the
respective predicate. In several cases, the predicate is
consulted by the parser, like when deciding whether to interpret
`-3' as a number or a fingering event.
* Music functions (and their close relatives) can now be defined with
optional arguments.
* For defining commands executed only for their side-effects,
`define-void-function' is now available.
* There is a new `define-event-function' command in analogy to
`define-music-function' that can be used for defining music
functions acting as post events without requiring a direction
specifier (`-', `^', or `_') placed before them.
dyn=#(define-event-function (parser location arg) (markup?)
(make-dynamic-script arg))
\relative c' { c\dyn pfsss }
* A list of ASCII aliases for special characters can be included.
\paper {
#(include-special-characters)
}
\markup "• † ©right; &OE; &ss; ¶"
* There is a new `define-scheme-function' command in analogy to
`define-music-function' that can be used to define functions
evaluating to Scheme expressions while accepting arguments in
Lilypond syntax.
* The construct `#{ ... #}' can now be used not just for
constructing sequential music lists, but also for pitches
(distinguished from single note events by the absence of a
duration or other information that can't be part of a pitch),
single music events, void music expressions, post events, markups
(mostly freeing users from having to use the `markup' macro),
markup lists, number expressions, context definitions and
modifications, and a few other things. If it encloses nothing or
only a single music event, it no longer returns a sequential music
list but rather a void music expression or just the music event
itself, respectively.
* Pitches can be used on the right side of assignments. They are
distinguished from single note events by the absence of a duration
or other information that can't be part of a pitch.
* New command-line option `--loglevel=LEVEL' to control how much
output LilyPond creates. Possible values are ERROR, WARN,
BASIC_PROGRESS, PROGRESS, DEBUG.
* `\once \set' now correctly resets the property value to the
previous value.
* The alignment of dynamic spanners (hairpins, text crescendo, etc.)
is now automatically broken if a different direction is explicitly
given.
* Appoggiaturas and acciaccaturas now also work inside a slur, not
only inside a phrasing slur. Also, a function `\slashedGrace' was
added that does not use a slur from the acciaccatura note.
* To suppress the line on a crescendo text spanner (and other
similar spanners), LilyPond now fully supports the `#'style =
#'none' property.
* LilyPond.app now supports MacOS X 10.7, thanks Christian Hitz!
* Glissandi can now span multiple lines.
|
|
|
|
|
|
|
|
|
|
Alex Deucher (1):
radeon: add new SI pci id
Ben Skeggs (2):
nouveau: disallow pushbuf BOs in multiple memory types
nouveau: expose channel engine selection on kepler chipsets
Chris Wilson (1):
intel: Remove the fence count contributions when clearing relocs
David Herrmann (4):
man: convert manpages to XML instead of plain troff
man: add drm.7 overview page
man: add drm-kms overview page
man: add drm-memory overview page
David Shao (1):
intel: Fix missing ETIME on BSD operating systems
Jerome Glisse (1):
drm/radeon: track global bo name and always return the same
Jesse Barnes (1):
man: disable man page building until David saves us all
Maarten Lankhorst (1):
configure.ac: bump version to 2.4.41 for release
Marcin Slusarz (1):
libdrm_nouveau.pc: don't include I${includedir}/nouveau
Maxime Villard (2):
libkms: fix memory leak in error path
libkms: return -EINVAL on fstat error
|
|
|
|
Version 1.23 - 24 Jan 2013
* New message retrieval backend Locale::gettext_dumb(3pm) which produces
translations even, when the corresponding locale is not present in
the system.
* Fixed a bug where the Perl backend under certain circumstances clobbered
the environment variable LC_ALL.
* Avoid test failures by skipping all tests that depend on the de_AT
locale, when that locale is not installed.
* Bugs fixed:
https://rt.cpan.org/Ticket/Display.html?id=82856
Version 1.22 - 24 Jan 2013
* Version 1.22 outsmarted PAUSE (the CPAN upload facility) and had to
be removed.
Version 1.21 - 15 Jan 2013
* Environment variables LANGUAGE and LANG are interpreted in the same way
in the XS and the pure Perl version.
* Package design closer to GNU standards.
* If present, File::ShareDir is used for searching message catalogs.
* Cleaned up distribution.
* Bugs fixed:
https://rt.cpan.org/Ticket/Display.html?id=78341
https://rt.cpan.org/Ticket/Display.html?id=81315
https://rt.cpan.org/Ticket/Display.html?id=79461
https://rt.cpan.org/Ticket/Display.html?id=71509
https://rt.cpan.org/Ticket/Display.html?id=49744
https://rt.cpan.org/Ticket/Display.html?id=49744
https://rt.cpan.org/Ticket/Display.html?id=64284
|
|
|
|
on NetBSD/arm where boost could not determine the endianness.
(patch has been submitted upstream)
|
|
|
|
|
|
|
|
|
|
Add cjpeg -rgb1 option to create an RGB JPEG file, and insert
a simple reversible color transform into the processing which
significantly improves the compression.
The recommended command for lossless coding of RGB images is now
cjpeg -rgb1 -block 1 -arithmetic.
As said, this option improves the compression significantly, but
the files are not compatible with JPEG decoders prior to IJG v9
due to the included color transform.
The used color transform and marker signaling is compatible with
other JPEG standards (e.g., JPEG-LS part 2).
Remove the automatic de-ANSI-fication support (Automake 1.12).
Add remark for jpeg_mem_dest() in jdatadst.c.
Support files with invalid component identifiers (created by Adobe PDF).
Adapt full buffer case in jcmainct.c for use with scaled DCT.
Add type identifier for declaration of noreturn functions.
Correct argument type in format string, avoid compiler warnings.
Add missing #include directives in configuration checks, avoid
configuration errors.
|
|
|
|
Version 1.7.43 (built with libpng-1.5.13 and zlib-1.2.7)
Added "remove(inname)" before "rename(outname, inname)" when using the "-ow"
option on CYGWIN/MinGW because "rename()" does not work if the target file
exists.
Use the bundled "zlib.h" when PNGCRUSH_H is defined, otherwise use the
system .
Version 1.7.42 (built with libpng-1.5.13 and zlib-1.2.7)
Use malloc() and free() instead of png_malloc_default() and
png_free_default(). This will be required to run with libpng-1.7.x.
Revised the PNG_ABORT definition in pngcrush.h to work with libpng-1.7.x.
Revised zutil.h to avoid redefining ptrdiff_t on MinGW/CYGWIN platforms.
|
|
PR pkg/45814, also reported upstream at
<https://rt.perl.org/rt3/Public/Bug/Display.html?id=116523>.
Not bumping PKGREVISION because there should be no change in
the resulting package, on systems where the build was successful.
|
|
|
|
Changelog:
QMP
The sendkey monitor command is now available via QMP.
All targets
QEMU can now use the Linux VFIO driver to assign PCI devices to a virtual machine.
The bus master configuration bit for PCI devices is now emulated. PCI devices cannot anymore perform DMA without setting the bit before. This may break firmware that wasn't tested on real hardware.
MIPS
Loongson Multimedia Instructions are now implemented.
MIPS32/64 ASE DSP Instructions are now implemented.
x86
The TSC frequency can be larger than 2.147 GHz.
Configuration files do not support anymore the cpudef section.
TCG (emulation) supports the SMEP (Supervisor Mode Execution Prevention) and SMAP (Supervisor Mode Access Prevention) features of newer x86 processors.
CPUID/models?
The "cpudef" config file section is now deprecated and will be removed in v1.4.
New CPU models: "Haswell" (new features: fma, pcid, movbe, fsgsbase, bmi1, hle, avx2, smep, bmi2, erms, invpcid, rtm) and "Opteron_G5" (new features: tbm, f16c, fma)
Added Intel Q35 chipset as a new machine type, '--machine q35'. Adds PCIe support. Requires an updated SeaBIOS (bios.bin), and '-acpitable file=/seabios-path/q35-acpi-dsdt.aml' to run.
Xtensa
Single precision floating point instructions are now implemented.
Device emulation
Emulation of the MC146818 real-time clock (used on PC and several other boards) does not wake up QEMU anymore every second to update the clock.
USB3 has been vastly improved, including support for USB mass storage devices and MSI/MSI-X support for the XHCI controller.
USB redirection now supports live migration.
Several bugs in the AHCI controller were fixed to support recent Windows versions.
ivshmem now has a "use64" property which will make the ivshmem driver register a 64-bit memory BAR.
New paravirtualized hardware random number generator device, VirtIORNG.
Network devices
Some problems were fixed leading to bad receive performance of E1000 and Xen network cards.
Block devices
qemu-img now can output information in JSON format using "qemu-img info --output=json".
Glusterfs volumes can be accessed with "gluster://" URIs for "-drive" and similar options. Optionally the transport can also be specified, as in "gluster+tcp://" (other supported transports are "unix" and "rdma").
Options on the QMP streaming command direct the job to pause on encountering errors, or to ignore them altogether.
A new block job is supported: live block commit (also known as "snapshot deletion") moves data from an image to another in the backing file chain. With the current implementation of QEMU 1.3, the "source" image may not be the active one.
A new block job is supported: live disk mirroring (also known as "storage migration") moves data from an image to another. A new command "block-job-complete" is used to switch the VM to use the destination image exclusively.
Block jobs can now be paused and resumed from the monitor.
NBD block devices can now be specified using URI syntax. "nbd://" defaults to TCP transport, while "nbd+tcp://" and "nbd+unix://" can be used (similar to Gluster) to specify it. URI syntax simplifies access to named exports; the export name is simply the "path" component of the URI.
NBD connections to Unix sockets support relative paths.
QEMU embeds an NBD server, accessible via the monitor. The NBD server allows live access to the image seen by the VM. Note that the embedded server uses "named exports", which QEMU can access using the "nbd://host:port/name" syntax.
Windows hosts support asynchronous disk I/O.
Live Migration, Save/Restore
The "stop" and "cont" commands have new semantics on the destination machine during migration. Previously, the outcome depended on whether the commands were issued before or after the source connected to the destination QEMU: in particular, "cont" would fail if issued before connection, and "undo" the effect of the -S command-line option if issued after. Starting from this version, the effect of "stop" and "cont" will always take place at the end of migration (overriding the presence or absence of the -S option) and "cont" will never fail. This change should be transparent, since the old behavior was usually subject to a race condition.
The monitor now remains responsive during incoming migration. The new NBD server is also available during incoming migration.
Spice
QEMU will only send changed screen content to the Spice client when running in legacy VGA mode.
Seamless migration support.
Composite QXL commands (for linux guests).
Multiple monitors on a single pci device.
Arbitrary resolution support.
Device based monitor configuration notification (for future drivers).
various bug fixes and assertion removals in favor of a guest_bug mode.
require spice-server >= 0.12.0
KVM
QEMU now supports "old-style" PCI device assignment, which was the last missing feature from the qemu-kvm fork. Despite some remaining minor differences between qemu-kvm and QEMU, it is possible to switch from qemu-kvm to QEMU as soon as your guests can be rebooted. Live migration from qemu-kvm 1.2 to QEMU 1.3 is not supported, but can be enabled easily by downstream distributions who want to switch their packages from qemu-kvm to QEMU.
Xen
QEMU can now be used to live-migrate Xen domains.
SLIRP
SLIRP's TFTP server has improved performance, can transmit files bigger than 32 MB, and supports the block size option.
Guest agent
The guest agent will now store the state file in /var/run by default.
Host support
SPARCv7 and v8 support was removed.
Build dependencies
QEMU can now be built with Clang.
QEMU now uses pixman. QEMU configure will detect and use a system pixman if the development headers are ailable (they should be available for most recent Linux distros). As a fallback, we provide an internal copy of the pixman sources which will be used if there is no set of system pixman libraries. Compiling these will require autoconf.
Compiling QEMU ver 0.12 or better.
|
|
|
|
|
|
================
Changes in PyZMQ
================
2.2.0.1
=======
This is a tech-preview release, to try out some new features.
It is expected to be short-lived, as there are likely to be issues to iron out,
particularly with the new pip-install support.
Experimental New Stuff
----------------------
These features are marked 'experimental', which means that their APIs are not set in stone,
and may be removed or changed in incompatible ways in later releases.
Threadsafe ZMQStream
********************
With the IOLoop inherited from tornado, there is exactly one method that is threadsafe:
:meth:`.IOLoop.add_callback`. With this release, we are trying an experimental option
to pass all IOLoop calls via this method, so that ZMQStreams can be used from one thread
while the IOLoop runs in another. To try out a threadsafe stream:
.. sourcecode:: python
stream = ZMQStream(socket, threadsafe=True)
pip install pyzmq
*****************
PyZMQ should now be pip installable, even on systems without libzmq.
In these cases, when pyzmq fails to find an appropriate libzmq to link against,
it will try to build libzmq as a Python extension.
This work is derived from `pyzmq_static <https://github.com/brandon-rhodes/pyzmq-static>`_.
To this end, PyZMQ source distributions include the sources for libzmq (2.2.0) and libuuid (2.21),
both used under the LGPL.
zmq.green
*********
The excellent `gevent_zeromq <https://github.com/traviscline/gevent_zeromq>`_ socket
subclass which provides `gevent <http://www.gevent.org/>`_ compatibility has been merged as
:mod:`zmq.green`.
.. seealso::
:ref:`zmq_green`
Bugs fixed
----------
* TIMEO sockopts are properly included for libzmq-2.2.0
* avoid garbage collection of sockets after fork (would cause ``assert (mailbox.cpp:79)``).
2.2.0
=====
Some effort has gone into refining the pyzmq API in this release to make it a model for
other language bindings. This is principally made in a few renames of objects and methods,
all of which leave the old name for backwards compatibility.
.. note::
As of this release, all code outside ``zmq.core`` is BSD licensed (where
possible), to allow more permissive use of less-critical code and utilities.
Name Changes
------------
* The :class:`~.Message` class has been renamed to :class:`~.Frame`, to better match other
zmq bindings. The old Message name remains for backwards-compatibility. Wherever pyzmq
docs say "Message", they should refer to a complete zmq atom of communication (one or
more Frames, connected by ZMQ_SNDMORE). Please report any remaining instances of
Message==MessagePart with an Issue (or better yet a Pull Request).
* All ``foo_unicode`` methods are now called ``foo_string`` (``_unicode`` remains for
backwards compatibility). This is not only for cross-language consistency, but it makes
more sense in Python 3, where native strings are unicode, and the ``_unicode`` suffix
was wedded too much to Python 2.
Other Changes and Removals
--------------------------
* ``prefix`` removed as an unused keyword argument from :meth:`~.Socket.send_multipart`.
* ZMQStream :meth:`~.ZMQStream.send` default has been changed to `copy=True`, so it matches
Socket :meth:`~.Socket.send`.
* ZMQStream :meth:`~.ZMQStream.on_err` is deprecated, because it never did anything.
* Python 2.5 compatibility has been dropped, and some code has been cleaned up to reflect
no-longer-needed hacks.
* Some Cython files in :mod:`zmq.core` have been split, to reduce the amount of
Cython-compiled code. Much of the body of these files were pure Python, and thus did
not benefit from the increased compile time. This change also aims to ease maintaining
feature parity in other projects, such as
`pyzmq-ctypes <https://github.com/svpcom/pyzmq-ctypes>`_.
New Stuff
---------
* :class:`~.Context` objects can now set default options when they create a socket. These
are set and accessed as attributes to the context. Socket options that do not apply to a
socket (e.g. SUBSCRIBE on non-SUB sockets) will simply be ignored.
* :meth:`~.ZMQStream.on_recv_stream` has been added, which adds the stream itself as a
second argument to the callback, making it easier to use a single callback on multiple
streams.
* A :attr:`~Frame.more` boolean attribute has been added to the :class:`~.Frame` (née
Message) class, so that frames can be identified as terminal without extra queires of
:attr:`~.Socket.rcvmore`.
Experimental New Stuff
----------------------
These features are marked 'experimental', which means that their APIs are not
set in stone, and may be removed or changed in incompatible ways in later releases.
* :mod:`zmq.web` added for load-balancing requests in a tornado webapp with zeromq.
|
|
|
|
passes upstream's test now.
|
|
|
|
0MQ version 2.2.0 (Stable), released on 2012/04/04
==================================================
Changes
-------
* Fixed issue 349, add send/recv timeout socket options.
Bug fixes
---------
* Fixed issue 301, fix builds on HP-UX 11iv3 when using either gcc or aCC.
* Fixed issue 305, memory leakage when using dynamic subscriptions.
* Fixed issue 332, libzmq doesn't compile on Android NDK.
* Fixed issue 293, libzmq doesn't follow ZMTP/1.0 spec.
* Fixed issue 342, cannot build against zmq.hpp under C++11.
|
|
Mac OS X Mountain Lion's "sed" will otherwise reject some patch files
(e.g. "pkgsrc/devel/libcfg+/patches/patch-ab") because of broken
UTF-8 encoding.
It would probably be better not to use the bundled "sed" under
Mac OS X Mountain Lion at all. But it seems that this is not
supported by "pkgsrc" at the moment.
|
|
|
|
|
|
|
|
=== 0.7.7 / 22.01.2013
Author: DeTeam <timur.deteam@gmail.com>
Date: Tue Jan 22 19:11:52 2013 +0400
* Make tests pass
* Readme updated
* RuntimeError when file is empty
* Hoe in dev deps
* Finish with bundler
* Add a Gemfile
also see: https://github.com/zdavatz/spreadsheet/pull/24
|
|
|
|
Bump PKGREVISION.
|
|
|
|
of Xcode under Mac OS X.
|
|
Bump PKGREVISION.
|
|
|
|
Changes since the last public release (1.5.13):
Added -DZ_SOLO to contrib/pngminim/*/makefile to work with zlib-1.2.7
Warn about the incorrect runtime library setting for VS2010 debug DLL builds.
Fixed build when using #define PNG_NO_READ_GAMMA in png_do_compose() in
pngrtran.c (Domani Hannes).
Check for png_ptr==NULL earlier in png_zalloc().
Ignore, with a warning, out-of-range value of num_trans in png_set_tRNS().
Rearranged building of ARM NEON optimizations. The ARM specific code is
split out entirely to the arm subdirectory and changes to configure.acand
Makefile.am to add new stuff are reduced. Now material code changes,
although for build test purposes, --enable-arm-neon now builds on non-ARM
systems.
Rebuilt Makefile.in, configure, etc., with autoconf-2.69 and automake-1.12.5.
Fixed cases of unquoted DESTDIR in Makefile.am
Fixed a minor bug in types to malloc and major bug in handling compressed
iTXt. Compressed iTXt could not be handled.
Cleaned up whitespace in the synopsis portion of the manpage "libpng.3"
Disassembled the version number in scripts/options.awk (necessary for
building on SunOs).
Fixed Windows build issues, enabled ARM compilation. Various warnings issued
by earlier versions of GCC fixed for Cygwin and Min/GW (which both use old
GCCs.) ARM support is enabled by default in zlib.props (unsupported by
Microsoft) and ARM compilation is made possible by deleting the check for
x86. The test programs cannot be run because they are not signed.
Fixed 'make distcheck' on SUN OS - libpng.so was not being removed
Replaced AM_CONFIG_HEADER(config.h) with AC_CONFIG_HEADERS([config.h])
in configure.ac
De-configured build fixes to make a range of deconfiguration options (such
as switching off read or write support) work in more cases. Also upgraded
pngtest and pngvalid to the libpng 1.6 versions (with some modifications)
which provide more extensive testing. Replaced pngtest.png because pngtest
writes the ancillary chunks in a different order.
Check validity of "num_unknowns" parameter of png_set_unknown_chunks()
(Bug report from yuris).
Check the validity of the "nentries" parameter of png_set_sPLT() and the
"num_text" parameter of png_set_text_2().
|
|
|
|
|
|
Update LICENSE
Upstream changes:
genetics 1.3.8 - 2012-12-14
---------------------------
Bug fixes:
- Regenerate broken PDF files in inst/doc.
genetics 1.3.7 - 2012-09-14
---------------------------
Enhancements:
- Improve descripiton of last examples in manual page for HWE.test().
Other Changes:
- Correct warnings issued by recent versions of R CMD CHECK.
|
|
|
