* pkgsrc change: require ruby-rdoc version 3.9.4 or later to build
problem on ruby18 and ruby19.
Exact changes aren't available, please refer:
https://github.com/ffi/ffi/commits/master
Based on PR pkg/46549 by Wen Heping(myself)
Upstream changes:
1.5017 Wed Jul 18 08:28:49 PDT 2012
[Improvements]
- Ignore tarballs whose first entry is "./" (doy) #184
1.5016 Tue Jul 17 12:00:57 PDT 2012
[Improvements]
- Added Module/CPANfile.pm to the fatlib. This allows bootstrapping dependencies
with cpanm --installdeps on Heroku etc.
1.5015 Sun Jun 24 15:34:57 PDT 2012
[Improvements]
- Improved Makefile.PL to include bugtracker info (Ben Bullock)
- Fixed some merge mess with devel
1.5014 Tue Jun 12 18:27:02 PDT 2012
[Improvements]
- Make sure 'f' flag becomes the last for some tar versions (mst, aaronsw)
- Fixed warnings on perl 5.17+ (rjbs)
- Fix local::lib error message (berekuk)
1.5013 Sat May 12 06:15:44 EEST 2012
[Bug Fixes]
- Fixed --cascade-search to seach for missing modules, which was broken by #150
1.5012 Fri May 11 05:47:56 CEST 2012
[Improvements]
- Change the behavior of --mirror-index so that it won't fallback to CPAN mirrors #150 (thaljef)
- Support v-strings in versions specified install [https://github.com/miyagawa/carton/issues/48]
1.5011 Thu Apr 12 18:57:06 JST 2012
[Improvements]
- Point default mirror to www.cpan.org #148
1.5010 Sat Mar 31 12:59:52 CEST 2012
[New Feature]
- Implemented --test-only option #40
1.5009 Fri Mar 30 18:44:12 CEST 2012
[Bug Fixes]
- Fixed a bug where URL containing ~ (childe) fails to install #134
- Fixed a bug where install.json contains bogus data when you specify dist paths
1.5008 Sat Mar 17 18:19:57 PDT 2012
[Bug Fixes]
- Fied a bug where `cpanm Foo` doesn't properly activate local::lib during installs
when you don't have write permissions #143 (goodel, ash)
- Improved the warning message when you don't have write permisisons #145 (ash)
=== Cutter
==== Improvements
* [UI][GTK+] Supported GTK+ < 2.22 for Debian GNU/Linux squeeze.
* [UI][console] Supported growlnotify.exe for windows.
* [UI][GTK+] Added menubar.
* [UI][GTK+] Improved to log an error message for showing URI.
* [UI][GTK+] Supported --with-fallback-browser option to customize
fallback browser.
* Improved to use "()" as a part of function about backtrace.
* [UI][console] Added more color acceptable TERMs
(xterm-256color, screen-256color, screen-color)
* Added Travis CI integration.
* Supported backtrace on SIGBUS [Patch by Kiwamu Okabe]
* Added Homebrew related paths by default on Mac OS X.
==== Changes
* [doc][Mac OS X] Recommended to use the official MacPorts repository.
[Suggested by Hiroshi Umemoto]
* Supported Fedora 17.
* Dropped Fedora 16 support.
* Supported Ubuntu Precise.
==== Fixes
* [Clang] Fixed not to add extra "()" for function name of backtrace.
* Fixed compilation failure on MinGW.
=== CppCutter
==== Improvements
* Supported nested namespace test case built by g++
PLIST of doxygen varies depending on graphviz configuration.
Say, graphviz configured with PKG_OPTIONS.pangocairo yes or no.
Graphviz/buildlink3.mk will set PKG_BUILD_OPTIONS.graphviz
for use with doxygen PLIST variation.
Thanks Ian McWilliam for reporting and testing the problem.
This is an update of the package to its newest version. There are no changes
in functionality, only in the build system. The package itself has also been
improved slightly (use of PLIST_VARS, most notably).
Despite its pretentious name, this package is just an attempt to generalize
a bunch of code that I keep reusing every time I implement shell scripts.
In particular, this is about to remove tons of duplicate stuff from both
sysbuild and sysupgrade in subsequent commits and I'll probably use it again
for some other stuff I have in mind.
Description follows:
The Shell Toolkit, or shtk for short, is a collection of modules written in
sh(1) that provide common functionality to simplify the implementation of
complex shell scripts. These modules provide things like utilities to
manipulate data types, helpers to expose a common CLI, or higher-level
abstractions such as the processing of configuration files.
The included shtk(1) utility exposes convenience functionality to let the
user "build" shell scripts that use shtk. Build, in this case, just means
adding common boilerplate code to the initialization of the script to load
the shtk common code.
New in 1.12.3:
* WARNING: Future backward-incompatibilities!
- Future versions of Automake will likely drop support for the
long-deprecated 'configure.in' name for the Autoconf input file.
You are advised to use the recommended name 'configure.ac' instead.
- The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will
be removed in Automake 1.13. The $(mkdir_p) make variable and the
@mkdir_p@ substitution will still remain available (as aliases of
$(MKDIR_P)) for the moment, for better backward compatibility.
- Autoconf 2.65 or later will be required by the next major Automake
version (1.13). Until now, Automake has required Autoconf version
2.62 or later.
- Starting from the next major Automake version (1.13), the rules
to build pdf, ps and dvi output from Texinfo input will use the
'--build-dir' option by default. Since such an option was only
introduced in Texinfo 4.9, this means that Makefiles generated by
future Automake versions will require at least that version of
Texinfo.
- Starting from the next major Automake version (1.13), the parallel
testsuite harness (previously only enabled by the 'parallel-tests'
option) will become the default one; the older serial testsuite
harness will still be available through the use of the 'serial-tests'
option.
- The following long-obsolete m4 macros will be removed in the
next major Automake version (1.13):
AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
of the now-removed automatic de-ANSI-fication
support of Automake)
- All the "old alias" macros in 'm4/obsolete.m4' will be removed in
the next major Automake version (1.13).
- Support for the two- and three-arguments invocation forms of the
AM_INIT_AUTOMAKE macro is deprecated, and will be removed in the
next major Automake version (1.13).
- The '--acdir' option of aclocal is deprecated, and will probably
be removed in the next major Automake release (1.13). You should
use the options '--automake-acdir' and '--system-acdir' instead
(which have been introduced in Automake 1.11.2).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.13).
- The 'missing' script will not try anymore to update the timestamp
of out-of-date files that require a maintainer-specific tool to be
remade, in case the user lacks such a tool (or has a too-old version
of it). In fact, starting from Automake 1.13, all it'll do will be
giving more useful warnings than a bare "command not found" from a
make recipe would.
* Miscellaneous changes:
- The '.m4' files provided by Automake does not define serial numbers
anymore. This should cause no difference in the behaviour of aclocal
though.
- Some testsuite weaknesses and spurious failures have been fixed.
- There is initial support for automatic dependency tracking with the
Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
Bugs fixed in 1.12.3:
* Long-standing bugs:
- Instead of renaming only self-references of files (typically for
#lines), ylwrap now also renames references to the other generated
files. This fixes support for GLR and C++ parsers from Bison (PR
automake/491 and automake bug#7648): 'parser.c' now properly
#includes 'parser.h' instead of 'y.tab.h'.
- Generated files unknown to ylwrap are now preserved. This fixes
C++ support for Bison (automake bug#7648): location.hh and the
like are no longer discarded.
This is a maintainer update of devel/ocaml-lwt to its newest version, 2.4.0. The
changelog (bugfixes and some enhancements, plus compatibility with ocaml 4.00,
though it should still compile with ocaml 3.12):
- Reimplement Lwt_stream
much simpler and more efficient
do not use Weak
add bounded push streams
- Add Lwt.async
- Add Lwt_preemptive.run_in_main
- Implement Lwt_unix.get_credentials on MacOS X/OpenBSD
- Ensure that on_cancel functions are executed first
- Better implementation of Lwt.cancel with more tests
- Simplify the API for unix jobs
- Better handling of the master lock in libev stubs
- Windows fixes/updates:
pass -lws2_32 instead of ws2_32.lib if building with mingw
fix a bug causing Lwt_unix.read/write to block when a socket is not
readable/writable
port Lwt_process and Lwt_unix.system to windows
- Compatibility with ocaml 4.00:
add O_SHARE_DELETE to Lwt_unix.open_flag
add -package compiler-libs.toplevel for files using Toploop
- Do not use module Sys for signal handling to avoid ocaml code to be called in a C thread
- Fix Lwt_unix.wrap_syscall: try instead of Lwt.catch
- Fix a dead-lock between lwt_unix_send_notificati
- Fix#277: add a function to return the Ssl.socket of a Lwt_ssl.socket
There have also been a few changes to the package itself; it now uses
PLIST_VARS, and the patches are replaced by the SUBST mechanism.
A well-behaved Unix daemon process is tricky to get right, but the required
steps are much the same for every daemon program. A DaemonContext instance
holds the behaviour and configured process environment for the program; use
the instance as a context manager to enter a daemon state.
Collection.
The lockfile package exports a LockFile class which provides a simple API for
locking files. Unlike the Windows msvcrt.locking function, the fcntl.lockf and
flock functions, and the deprecated posixfile module, the API is identical
across both Unix (including Linux and Mac) and Windows platforms. The lock
mechanism relies on the atomic nature of the link (on Unix) and mkdir
(on Windows) system calls. An implementation based on SQLite is also provided,
more as a demonstration of the possibilities it provides than as
production-quality code.
Collection.
stompclient provides a simple and lighweight STOMP client API for Python.
stompclient supports both simplex (publisher-only) and duplex
(publish-subscribe) communication with STOMP servers. This project started as a
fork of the stompy project by Benjamin W. Smith) but has evolved into a very
distinct codebase, which combines a few ideas from stompy with features from
the Stomper library and CoilMQ broker.
0.16
Features
Enhancements to Cython's function type (support for weak
references, default arguments, code objects, dynamic attributes,
classmethods, staticmethods, and more)
Fused Types - Template-like support for functions and methods
CEP 522 (docs)
Typed views on memory - Support for efficient direct and indirect
buffers (indexing, slicing, transposing, ...) CEP 517 (docs)
super() without arguments
Final cdef methods (which translate into direct calls on known
instances)
General Improvements and Bug Fixes
support default arguments for closures
search sys.path for pxd files
support C++ template casting
faster traceback building and faster generator termination
support inplace operators on indexed buffers
fix alignment handling for record types in buffer support
allow nested prange sections
0.15.1
This is a bugfix-only release.
0.15
Major Features
Generators (yield) - Cython has full support for generators,
generator expressions and PEP 342 coroutines.
The nonlocal keyword is supported.
Re-acquiring the gil: with gil - works as expected within a
nogil context.
OpenMP support: prange.
Control flow analysis prunes dead code and emits warnings and
errors about uninitialised variables.
Debugger command cy set to assign values of expressions to
Cython variables and cy exec counterpart $cy_eval().
Exception chaining PEP 3134.
Relative imports PEP 328.
Improved pure syntax including cython.cclass, cython.cfunc,
and cython.ccall.
The with statement has its own dedicated and faster C
implementation.
Support for del.
Boundschecking directives implemented for builtin Python sequence
types.
Several updates and additions to the shipped standard library
.pxd files.
Forward declaration of types is no longer required for circular
references.
Note: this will be the last release to support Python 2.3; Python
2.4 will be supported for at least one more release.
General improvements and bug fixes
This release contains over a thousand commits including hundreds
of bugfixes and optimizations. The bug tracker has not been as
heavily used this release cycle, but is still an interesting subset
of improvements and fixes
Incompatible changes
Uninitialized variables are no longer initialized to None and
accessing them has the same semantics as standard Python.
globals() now returns a read-only dict of the Cython module's
globals, rather than the globals
of the first non-Cython module in the stack
Many C++ exceptions are now special cased to give closer Python
counterparts. This means that except+ functions that formerly
raised generic RuntimeErrors may raise something else such as
ArithmeticError.
Known regressions
The inlined generator expressions (introduced in Cython 0.13)
were disabled in favour of full generator expression support.
This breaks code that previously used them inside of cdef
functions (usage in def functions continues to work) and induces
a performance regression for cases that continue to work but
that were previously inlined. We hope to reinstate this feature
in the near future.
Generators (yield) - Cython has full support for generators,
generator expressions and PEP 342 coroutines.
The nonlocal keyword is supported.
Re-acquiring the gil: with gil - works as expected within a
nogil context.
OpenMP support: prange.
Control flow analysis prunes dead code and emits warnings and
errors about uninitialised variables.
Debugger command cy set to assign values of expressions to
Cython variables and cy exec counterpart $cy_eval().
Exception chaining PEP 3134.
Relative imports PEP 328.
Improved pure syntax including cython.cclass, cython.cfunc,
and cython.ccall.
The with statement has its own dedicated and faster C
implementation.
Support for del.
Boundschecking directives implemented for builtin Python sequence
types.
Several updates and additions to the shipped standard library
.pxd files.
Forward declaration of types is no longer required for circular
references.
Note: this will be the last release to support Python 2.3; Python
2.4 will be supported for at least one more release.
General improvements and bug fixes
This release contains over a thousand commits including hundreds
of bugfixes and optimizations. The bug tracker has not been as
heavily used this release cycle, but is still an interesting subset
of improvements and fixes
Incompatible changes
Uninitialized variables are no longer initialized to None and
accessing them has the same semantics as standard Python.
globals() now returns a read-only dict of the Cython module's
globals, rather than the globals
of the first non-Cython module in the stack
Many C++ exceptions are now special cased to give closer Python
counterparts. This means that except+ functions that formerly
raised generic RuntimeErrors may raise something else such as
ArithmeticError.
Known regressions
The inlined generator expressions (introduced in Cython 0.13)
were disabled in favour of full generator expression support.
This breaks code that previously used them inside of cdef
functions (usage in def functions continues to work) and induces
a performance regression for cases that continue to work but
that were previously inlined. We hope to reinstate this feature
in the near future.
0.14.1
New Features
The gdb debugging support was extended to include all major
Cython features, including closures.
raise MemoryError() is now safe to use as Cython replaces it
with the correct C-API call.
General improvements and bug fixes
The bug tracker has a list of the major improvements and fixes
Incompatible changes
Decorators on special methods of cdef classes now raise a
compile time error rather than being ignored.
In Python 3 language level mode (-3 option), the 'str' type is
now mapped to 'unicode', so that cdef str s declares a Unicode
string even when running in Python 2.
0.14
New Features
Python classes can now be nested and receive a proper closure
at definition time.
Redefinition is supported for Python functions, even within
the same scope.
Lambda expressions are supported in class bodies and at the
module level.
Metaclasses are supported for Python classes, both in Python
2 and Python 3 syntax. The Python 3 syntax (using a keyword
argument in the type declaration) is preferred and optimised
at compile time.
"final" extension classes prevent inheritance in Python space.
This feature is available through the new "cython.final"
decorator. In the future, these classes may receive further
optimisations.
"internal" extension classes do not show up in the module
dictionary. This feature is available through the new
"cython.internal" decorator.
Extension type inheritance from builtin types, such as "cdef
class MyUnicode(unicode)", now works without further external
type redeclarations (which are also strongly discouraged now
and continue to issue a warning).
GDB support. http://docs.cython.org/src/userguide/debugging.html
A new build system with support for inline distutils directives,
correct dependency tracking, and parallel compilation.
http://wiki.cython.org/enhancements/distutils_preprocessing
Support for dynamic compilation at runtime via the new
cython.inline function and cython.compile decorator.
http://wiki.cython.org/enhancements/inline
General improvements and bug fixes
In parallel assignments, the right side was evaluated in reverse
order in 0.13. This could result in errors if it had side
effects (e.g. function calls).
In some cases, methods of builtin types would raise a SystemError
instead of an AttributeError when called on None.
Constant tuples are now cached over the lifetime of an extension
module, just like CPython does. Constant argument tuples of
Python function calls are also cached.
Closures have tightened to include exactly the names used in
the inner functions and classes. Previously, they held the
complete locals of the defining function.
"nogil" blocks are supported when compiling pure Python code
by writing "with cython.nogil".
The builtin "next()" function in Python 2.6 and later is now
implemented internally and therefore available in all Python
versions. This makes it the preferred and portable way of
manually advancing an iterator.
In addition to the previously supported inlined generator
expressions in 0.13, "sorted(genexpr)" can now be used as well.
Typing issues were fixed in "sum(genexpr)" that could lead to
invalid C code being generated. Other known issues with inlined
generator expressions were also fixed that make upgrading to
0.14 a strong recommendation for code that uses them. Note that
general generators and generator expressions continue to be
not supported.
Iterating over arbitrary pointer types is now supported, as is
an optimized version of the in operator, e.g. x in ptr[a:b].
Inplace arithmetic operators now respect the cdivision directive
and are supported for complex types.
Incompatible changes
Typing a variable as type "complex" previously gave it the
Python object type. It now uses the appropriate C/C++ double
complex type. A side-effect is that assignments and typed
function parameters now accept anything that Python can coerce
to a complex, including integers and floats, and not only
complex instances.
Large integer literals pass through the compiler in a safer
way. To prevent truncation in C code, non 32-bit literals are
turned into Python objects if not used in a C context. This
context can either be given by a clear C literal suffix such
as "UL" or "LL" (or "L" in Python 3 code), or it can be an
assignment to a typed variable or a typed function argument,
in which case it is up to the user to take care of a sufficiently
large value space of the target.
Python functions are declared in the order they appear in the
file, rather than all being created at module creation time.
This is consistent with Python and needed to support, for
example, conditional or repeated declarations of functions. In
the face of circular imports this may cause code to break, so
a new --disable-function-redefinition flag was added to revert
to the old behavior. This flag will be removed in a future
release, so should only be used as a stopgap until old code
can be fixed.
pkg-config 0.27
===
- Drop usage of popt for equivalent API in glib2.
- Add back an internal snapshot of glib2 to break circular dependency.
This can be used by passing --with-internal-glib to configure. On
Windows it may still be required to use an installed glib.
- Fix --exists to check for Requires and Requires.private. This ensures
that all necessary packages are installed prior to using --cflags,
--libs, etc.
- Various fixes for MinGW which should allow it to be used unpatched on
that system.
- New autoconf macros PKG_INSTALLDIR and PKG_NOARCH_INSTALLDIR to help
determine the .pc file install directory.
- Fix handling of --exact/atleast/max-version vs. =/>=/<=.
- Fix errors in man page source.
- Ensure testing only searches in the check directory.
- Bump glib requirement to 2.16 to avoid deprecated
g_win32_get_package_installation_subdirectory().
- Autotools refresh and update. The required versions now are
autoconf-2.62, automake-1.11 and libtool-2.2.
- Use g_alloca from glib instead of figuring out alloca ourselves.
- Remove search for setresuid & setreuid only needed for internal popt.
- Bugs fixed: 833, 2458, 5214, 5326, 5703, 6074, 8653, 9135, 9143,
9584, 10652, 11464, 14396, 17053, 23922, 28776, 29011, 29801, 31699,
31700, 32622, 34382, 37266, 39646, 41081, 43149, 44843, 45599, 45742,
48743
pkg-config 0.26
===
- Build system fixes
- More tests
- pkg.m4 fixups which makes autoconf 2.66 happier.
- Drop support for legacy -config scripts. Those should already be
gone and cause problems in cross-compilation environments.
- Drop embedded glib
- Fix up pkg.m4 to handle the case of --exists working and --cflags
or --libs failing.
- Various documentation updates
- Allow $() through without escaping it.
- Add --with-system-include-path instead of hard-coding
/usr/include.
New in CppUnit 1.13.0:
----------------------
* Portability:
- Added support for macro CPPUNIT_UNIQUE_COUNTER to config-*.h. It
should expands to a unique number per translation unit. Default
to __LINE__ if not defined. Use __COUNTER__ on MSVS 7.0+.
(Bug #2031696)
* Compilation
- destructor of Message causes segfault when testing (rhbz#641350)
- use correct CPPUNIT_VERSION value (sf#2983798)
- allow -Werror builds
(various Libreoffice patches)
- finite in "ieeefp.h" instead of math.h on Solaris (sf#2912590)
- Fixed compilation issue with Microsoft Visual Studio.Net 2005/2008 and
added Visual Studio 2005/2010 projects (.vcproj/.vcxproj)
- Changes to build without warnings using gcc -Wall -W -ansi
(patch #1898225 contributed by dpkatz)
- Libraries flags such as "-ldl" are now in LDADD instead of LIBADD_DL
( patch #2807259 contributed by Jan Echternach).
- Fixed detection of cxxabi.h with gcc 4.3 in configure (bug #2796543).
- made TestCaseDecorator copy c'tor and operator= private (fdo#51317)
* Documentation
- Updated several false documentation entries (sf#2185407, sf#2186611)
* Test Plug-in Runner:
- fixed memory leak in TestPlugInRunnerDlg (#1721408)
* API have changed
Changelog:
The only change in NSPR 4.9.2 is the new functions to set and get thread names:
Bug 758837 - Add functions to set and get thread names
Collection.
An implementation of the Stomp protocol for Ruby.
STOMP is the Simple (or Streaming) Text Orientated Messaging Protocol.
STOMP provides an interoperable wire format so that STOMP clients can
communicate with any STOMP message broker to provide easy and widespread
messaging interoperability among many languages, platforms and brokers.
This is a regularly-scheduled feature release with numerous improvements and bugfixes.
1.1. Core features
help: add --keyword (-k) for searching help
hgweb: side-by-side comparison functionality
log: support --graph without graphlog extension
push: accept revset argument for --rev
merge: bookmarks will no longer automatically merge with unnamed heads or other bookmarks. Instead it picks heads with diverging bookmarks.
introduce ChangesetsObsolescence concept (experimental)
bookmarks: allow existing remote bookmarks to become heads when pushing
bookmarks: pull new bookmarks from remote by default (backward incompatible change)
bookmarks: delete divergent bookmarks on merge
bisect: set HG_NODE when runing a command
graft: allow -r to specify revisions
graft: implement --log (issue3438)
graft: remark on empty graft
hooks: print out more information when loading a python hook fails
identity: show trailing '+' for dirty subrepos (issue2839)
incoming/outgoing: handle --graph in core
merge: warn about file deleted in one branch and renamed in other (issue3074)
Mercurial can now identify third-party extensions as sources of tracebacks
outgoing: accept revset argument for --rev
performance improvement on branchy repo: incrementaly update branchcache
performance improvement on huge file tree: add a C function to pack the dirstate
performance improvement for huge .hgignore: process regex with re2 bindings if available
revset: add "diff" field to "matching" predicate
revset: add "converted" predicate to find converted changesets
revset: add "origin" and "destination" predicates, to get graft, transplant or rebase origins or destinations.
revset: add "extra" predicate to match changesets extra fields (issue2767)
revset: add pattern matching to "bookmarks/branch/extra/tag/user" predicated
1.2. Extension features
acl: use of "!" prefix in user or group names
children: mark extension as deprecated
convert/svn: handle non-local svn destination paths (issue3142)
convert: accept Subversion 'file:///c%3A/svnrepo' syntax on Windows
fetch: mark extension as deprecated
graphlog: feature is now into core
histedit: new extension for interactive history editing
hg-ssh: add read-only flag
largefiles: add --all-largefiles flag to pull and clone (issue3188)
largefiles: improve performance by batching statlfile requests when pushing a largefiles repo (issue3386)
largefiles: no longer attempt to clone all largefiles to non-local destinations
largefiles: optimize performance when updating (issue3440)
largefiles: support revsets for cat, outgoing --large and revert
mq: introduce qpush/qpop/qgoto --keep-changes
strip: introduce -B option to remove a bookmark
rebase: allow collapsing branches in place (issue3111)
rebase: make --dest understand revsets
rebase: drop the infamous --detach option: rebase now behave with --source and --rev as expectable. It may no longer add second parent to rebased changeset (backward compatible change)
transplant: handle non-empty patches doing nothing (issue2806)
transplant: manually transplant pullable changesets with --log
1.3. Fixes
bisect: fix O(n**2) behaviour (issue3382)
bookmarks: fix push of moved bookmark when creating new branch heads
case insensitive file system can no longer be confused by -R on (issue2167)
copies: one fix related to directory rename detection (issue3511)
convert: check for failed svn import in debugsvnlog and abort cleanly
convert: ignore svn:executable for subversion targets without exec bit support
convert: keep branch switching merges with ancestors (issue3340)
convert: make filemap renames consistently override revision renames
debugrevlog: fix a bug with empty repository (issue3537)
graphlog: don't truncate template value at last \n
httprepo: ensure Content-Type header exists when pushing data
largefiles: fix a traceback when addremove follows a remove (issue3507)
largefiles: fix a traceback when archiving a subrepo in a subrepo
largefiles: fix addremove when largefile is missing (issue3227)
largefiles: fix addremove with -R option
largefiles: fix exception hack for i18n (issue3197)
largefiles: fix path handling for cp/mv (issue3516)
largefiles: archive -S now store largefiles instead of standins
largefiles: fix hg addremove when already removed largefile exists (issue3364)
merge: do not warn about copy and rename in the same transaction (issue2113)
mq: add ".hgsubstate" to patch target list only if it is not listed up yet
mq: create patch file after commit to import diff of ".hgsubstate" at qrefresh
pager: work around bug in python 2.4's subprocess module (issue3533):
revlog: zlib.error are no longer sent to the user (issue3424)
tag: don't allow tagging the null revision (issue1915)
changes: bugfixes (in particular a hash table problem)
pkgsrc changes:
-point to vala016 for regeneration of source files (which is only needed
after patches, not currently)
-add introspection support
Upstream changes:
1.000002 - 2012-08-04
- remove Devel::GlobalDestruction fallback inlining because we can now
depend on 0.08 which uses Sub::Exporter::Progressive
- honour BUILDARGS when calling $meta->new_object on behalf of Moose
- throw an error on invalid builder (RT#78479)
- fix stupid typo in new Sub::Quote section
1.000001 - 2012-07-21
- documentation tweaks and cleanup
- ignore required when default or builder is present
- document Moo versus Any::Moose in brief with article link
- remove quote_sub from SYNOPSIS and has docs, expand Sub::Quote section
- localize @_ when inlining quote_sub'ed isa checks (fixes lazy+isa+default)
- ensure constructor gets regenerated if forced early by metaclass inflation
1.000000 - 2012-07-18
- clean up doc language and expand on Moo and Moose
- error prefixes for isa and coerce exceptions
- unmark Moo and Moose as experimental since it's relatively solid now
- convert isa and coerce info from external role attributes
- clear method cache after metaclass generation to fix autoclean bug
Sub::Exporter is an incredibly powerful module, but with that power comes
great responsibility, er- as well as some runtime penalties. This module
is a Sub::Exporter wrapper that will let your users just use Exporter if
all they are doing is picking exports, but use Sub::Exporter if your users
try to use Sub::Exporter's more advanced features features, like renaming
exports, if they try to use them.
Note that this module will export @EXPORT and @EXPORT_OK package variables
for Exporter to work. Additionally, if your package uses advanced Sub::Exporter
features like currying, this module will only ever use Sub::Exporter, so
you might as well use it directly.
into devel/p5-Dist-Zooky.
Dist::Zooky is Dist::Zilla's nephew. He has the ability to summon his uncle.
dzooky will try its best to convert a distribution to use Dist::Zilla. It
supports ExtUtils::MakeMaker, Module::Install and Module::Build based
distributions, with certain limitations.
Simply execute dzooky in the directory containing the distribution you wish
to convert to Dist::Zilla.
* CheckIncludeFiles: Shorten check description message
* CPackNSIS: Rewrite variable documentation to make it more readable.
* OS X: Use correct extra path when searching for applicaton bundles
* OS X: Mark find_program results as advanced
* Fix some doc typo and add an undocumented var.
* OS X: Use OSX_DEVELOPER_ROOT for app search path
* FindBoost: add support for 1.49 and 1.50
* Bug fixes
Buffer overruns, complaints from Flex, and portability issues in the test
suite have been fixed.
* Spaces in %lex- and %parse-param (lalr1.cc, glr.cc)
Trailing end-of-lines in %parse-param or %lex-param would result in
invalid C++. This is fixed.
* Spurious spaces and end-of-lines
The generated files no longer end (nor start) with empty lines.
Bump dependency in buildlink3.mk since its only user is dconf-editor.
Set LICENSE.
Add comments to patches.
Changes in dconf 0.10.0
=======================
The version number was increased and a new entry was added to the NEWS.
Changes in dconf 0.9.1
======================
- give a g_warning() on failure to communicate with service
- remove unworking 'set lock' call from dconf API and commandline tool
- add code to exit gracefully on receipt of SIGINT, SIGHUP, SIGTERM
- remove "service function" logic; always use the XDG runtime directory
Changes in dconf 0.9.0
======================
There has been an extremely minor incompatible change in the D-Bus API
of dconf this release. From a practical standpoint, this change will
have no effect. However, it serves as a reminder that the dconf D-Bus
API is private and can change from version to version (and will likely
change in the future).
As such, it is appropriate for those packaging dconf to kill all running
instances of dconf ('killall dconf-service') as part of their postinst
for the package. It will be dbus-activated again on the next use.
- support loading/storing of maybe types in dconf
- remove NFS detection hackery and rely on XDG runtime dir
- add proper support for change notification to DConfClient
- commandline tool improvements
- reset: reset keys or entire subpaths
- dump: dump entire subpaths to keyfile format
- load: load them back again (maybe at a different path)
- watch: actually works now
- editor improvements
- keys now change in editor when changed from outside
- support for flags
- show dconf-editor in applications list
- work around incompatible Vala bindings changes with an #if
- don't install the bash completion script as executable
- fix a warning caused by reusing a GError variable
- other small fixes
Changes in dconf 0.7.5
======================
This release corrects a serious flaw in the previous release: crashing
if the database did not already exist.
It also contains many fixes and improvements to the dconf-editor,
including use of GSettings to store the window geometry.
This is the final release before 0.8.0 which will become the first
release in a new stable series. Feature development will continue on
'master' toward 0.9 past that point.
Changes in dconf 0.7.4
======================
Changes in this version:
- #648949: multithreading issue fixed (which actually affects all
GSettings-using programs since dconf is used from a helper thread in
that case)
- dconf commandline tool is vastly more friendly now
- no more aborting on unrecognised arguments
- proper help
- bash completion support
- support for sysadmin lockdown
- the editor now properly reads installed enum xml files
Changes in dconf 0.7.3
======================
This release consists almost entirely of fixes made by Robert to
dconf-editor. A few other trivial build fixes are included as well
(bumping library version dependencies to match reality, etc).
Changes in dconf 0.7.2
======================
This is entirely a cleanup/fixes release. Some fixes here to make the
increasingly-strict toolchain happy, and also some fixes for some
crashers in the GSettings backend and service.
- remove some unused variables (new GCC gives a warning: #640566, another)
- add a mutex to fix multi-threading issue (#640611)
- don't crash if we have no D-Bus
- clean up symbol exports
- fix a crash in the service when using 'reset'
- drop old linker options that were for libtool
Changes in dconf 0.7.1
======================
The last release contained a few problems that caused build failures on
some strict linkers. Those should be fixed now.
Changes in dconf 0.7
====================
- new library to use dconf with libdbus-1
- quite a lot of improvements and bug-fixes in dconf-editor, thanks to
Robert Ancell
- some bug fixes in the GSettings backend (crashers caused by use if
custom dconf profiles)
- some FreeBSD build fixes
- increased Vala dependency to 0.11.4 (required for dconf-editor fixes)
Changes in dconf 0.6
====================
- Rewrite a lot of the GSettings backend to reduce GDBus abuse. We use
our own worker thread now instead of trying to hijack GDBus's.
- disable gobject-introspection support for now
- drop support for GTK2 in dconf-editor
- Add a new torture-test case
- Increase dbus timeout to 2 minutes (in case the service is heavily loaded)
- Fix several memory leaks and other bugs
## Rails 3.2.7 (unreleased)
* `validates_inclusion_of` and `validates_exclusion_of` now accept `:within`
option as alias of `:in` as documented.
* Fix the the backport of the object dup with the ruby 1.9.3p194.
## Rails 3.2.7 (unreleased)
* Hash#fetch(fetch) is not the same as doing hash[key]
* adds a missing require [fixes#6896]
* make sure the inflection rules are loaded when cherry-picking
active_support/core_ext/string/inflections.rb [fixes#6884]
* Merge pull request #6857 from rsutphin/as_core_ext_time_missing_require
* bump AS deprecation_horizon to 4.0
mdds 0.6.0
* all
* added MSVS Solution file, to make it easier to build unit test
programs on Windows.
* mixed_type_matrix
* improved performance of size() method by caching it.
* multi_type_vector (new)
* new data structure to support efficient storage of data of different
types.
* multi_type_matrix (new)
* new data structure to eventually replace mixed_type_matrix. It uses
multi_type_vector as its backend storage.
packages needed to build pdf documentation, since there is no
configure option to disable it that I can see. If this leads to
problems, we'll have to disable it with a patch.
* version 2.5.36
** various portability fixes that quiet compiler warnings on 64-bit
hosts
** various manual fixes, including correcting the name of a %option and
updating some simple examples to use ANSI C syntax
** various bug fixes that prevent certain error conditions from
persisting when they should not persist
** improvements to the test suite so it behaves better when linking
compiled files
** new translations from the translation project: ca, da, es, fi, fr,
ga, ko, pt_br, ro, ru, sv, tr, zh_cn
** the flex distribution is now built with automake 1.10.1 and automake
2.61
* Noteworthy changes in release 2.6 (2012-07-19) [stable]
** Future Changes
The next major release of Bison will drop support for the following
deprecated features. Please report disagreements to bug-bison@gnu.org.
*** K&C parsers
Support for generating parsers in K&R C will be removed. Parsers
generated for C support ISO C90, and are tested with ISO C99 and ISO C11
compilers.
*** Features deprecated since Bison 1.875
The definitions of yystype and yyltype will be removed; use YYSTYPE and
YYLTYPE.
YYPARSE_PARAM and YYLEX_PARAM, deprecated in favor of %parse-param and
%lex-param, will no longer be supported.
Support for the preprocessor symbol YYERROR_VERBOSE will be removed, use
%error-verbose.
*** The generated header will be included (yacc.c)
Instead of duplicating the content of the generated header (definition of
YYSTYPE, yyparse declaration etc.), the generated parser will include it,
as is already the case for GLR or C++ parsers. This change is deferred
because existing versions of ylwrap (e.g., Automake 1.12.1) do not support
it.
** Generated Parser Headers
*** Guards (yacc.c, glr.c, glr.cc)
The generated headers are now guarded, as is already the case for C++
parsers (lalr1.cc). For instance, with --defines=foo.h:
#ifndef YY_FOO_H
# define YY_FOO_H
...
#endif /* !YY_FOO_H */
*** New declarations (yacc.c, glr.c)
The generated header now declares yydebug and yyparse. Both honor
--name-prefix=bar_, and yield
int bar_parse (void);
rather than
#define yyparse bar_parse
int yyparse (void);
in order to facilitate the inclusion of several parser headers inside a
single compilation unit.
*** Exported symbols in C++
The symbols YYTOKEN_TABLE and YYERROR_VERBOSE, which were defined in the
header, are removed, as they prevent the possibility of including several
generated headers from a single compilation unit.
*** YYLSP_NEEDED
For the same reasons, the undocumented and unused macro YYLSP_NEEDED is no
longer defined.
** New %define variable: api.prefix
Now that the generated headers are more complete and properly protected
against multiple inclusions, constant names, such as YYSTYPE are a
problem. While yyparse and others are properly renamed by %name-prefix,
YYSTYPE, YYDEBUG and others have never been affected by it. Because it
would introduce backward compatibility issues in projects not expecting
YYSTYPE to be renamed, instead of changing the behavior of %name-prefix,
it is deprecated in favor of a new %define variable: api.prefix.
The following examples compares both:
%name-prefix "bar_" | %define api.prefix "bar_"
%token <ival> FOO %token <ival> FOO
%union { int ival; } %union { int ival; }
%% %%
exp: 'a'; exp: 'a';
bison generates:
#ifndef BAR_FOO_H #ifndef BAR_FOO_H
# define BAR_FOO_H # define BAR_FOO_H
/* Enabling traces. */ /* Enabling traces. */
# ifndef YYDEBUG | # ifndef BAR_DEBUG
> # if defined YYDEBUG
> # if YYDEBUG
> # define BAR_DEBUG 1
> # else
> # define BAR_DEBUG 0
> # endif
> # else
# define YYDEBUG 0 | # define BAR_DEBUG 0
> # endif
# endif | # endif
# if YYDEBUG | # if BAR_DEBUG
extern int bar_debug; extern int bar_debug;
# endif # endif
/* Tokens. */ /* Tokens. */
# ifndef YYTOKENTYPE | # ifndef BAR_TOKENTYPE
# define YYTOKENTYPE | # define BAR_TOKENTYPE
enum yytokentype { | enum bar_tokentype {
FOO = 258 FOO = 258
}; };
# endif # endif
#if ! defined YYSTYPE \ | #if ! defined BAR_STYPE \
&& ! defined YYSTYPE_IS_DECLARED | && ! defined BAR_STYPE_IS_DECLARED
typedef union YYSTYPE | typedef union BAR_STYPE
{ {
int ival; int ival;
} YYSTYPE; | } BAR_STYPE;
# define YYSTYPE_IS_DECLARED 1 | # define BAR_STYPE_IS_DECLARED 1
#endif #endif
extern YYSTYPE bar_lval; | extern BAR_STYPE bar_lval;
int bar_parse (void); int bar_parse (void);
#endif /* !BAR_FOO_H */ #endif /* !BAR_FOO_H */
GCC 4.6 and newer on SunOS will force C99 with C++, which requires
_XOPEN_SOURCE=600 to be set. On the other hand, GCC 4.5 and earlier will
require C99 for _XOPEN_SOURCE=600, but reject C99 for C++ code.
Set _XOPEN_SOURCE to 500 or 600 accordingly.
* Fix for bug #679013 - AtspiCollection should be implemented for
all containers
* Plug ref count leaks (BGO#679285).
* Only add items to the cache on children-changed if the children are
included in the event.
* Only send PropertyChange signals used for caching, absent listeners.
Especially:
* Only create a directory and a socket when requested.
Currently, atk-bridge clutters XDG_RUNTIME_DIR with directories for sockets,
which is especially annoying since gtk currently does not call
atk_bridge_adaptor_cleanup, so the directories never go away. This change do
not really solve the problem--it only hides it from users who do not really
need AT-SPI--but, nevertheless, there is no reason to create a directory or
socket if nothing has requested it, so doing this lazily makes sense.
* Don't create a (non-readable) subdirectory for the socket when root.
If an application is running as root but within a user's runtime directory,
then creating a temporary directory will result in the directory being owned
by root, and the user will not have permission to search the directory to
access the socket, so an AT running as the normal user will not be able to
connect to the application running as root.
Fixes regression introduced by the fix for BGO#678348.
ChangeLog from last version:
SECURITY
========
* Close several XSS vulnerabilities in topic administration page. This
resolves CVE-2012-2768.
DOC
===
* Clarify that the only version incompatibility is 3.8.0; 3.8.x for
values of x != 0 is fine.
* Note incompatibility with RT 4 and above, which already include RTFM
functionality as "Articles"
XXX: for now disable copying of PO files, they conflict with RT ones.
