devel/p5-Lexical-SealRequireHints from 0.005nb2 to 0.007.
Upstream changes since 0.005:
version 0.007; 2012-02-11
* be thread-safe, by mutex control on op check hooking
* in pure Perl implementation, avoid putting extra eval stack frames
around the require, to avoid unnecessary complication of exception
handling; this can't be done on Perls 5.9.4 to 5.10.0, so don't
allow use of the pure Perl implementation on those Perls
* revise documentation to suggest loading this module earlier
* document the relevant changes to the Perl core in more detail
* on Perl versions where the pure Perl implementation can't work,
dynamically declare requirement for XS infrastructure in Build.PL
* refine threshold for ability to correctly override require from
5.8.0 to 5.7.2
* revise minimum required Perl version down from 5.6.1 to 5.6.0
* test that modules see the correct context at file scope
* test that module return values are handled correctly
* test that the module doesn't generate warnings
* in pure Perl implementation, fix handling of the variable that
previously needed to be "our"
* rearrange and better comment the treatment of lexical warnings in
the Perl code
version 0.006; 2011-11-20
* bugfix: avoid loading warnings.pm and leaving its delayed requires
of Carp.pm susceptible to hint leakage, which was causing trouble
on some Perls
* skip swash test on Perl 5.6, where swash loading appears to be broken
by loading Test::More or anything else useful
* remove bogus tests that cause false failures on Perl 5.15.5
* in Build.PL, declare incompatibility with pre-0.19
B::Hooks::OP::Check, which doesn't play nicely around op check hooking
* comment why a variable surprisingly needs to be "our"
* convert .cvsignore to .gitignore
devel/p5-indirect.
When enabled, this pragma warns about indirect method calls that are
present in your code.
This pragma currently does not warn for core functions (print, say, exec
or system). This may change in the future, or may be added as optional
features that would be enabled by passing options to unimport.
In http://www.shadowcat.co.uk/blog/matt-s-trout/indirect-but-still-fatal,
Matt S. Trout gives an example of an undesirable indirect method call on
a block that can cause a particularly bewildering error.
devel/p5-circular-require.
Perl by default just ignores cycles in require statements - if Foo.pm does
use Bar and Bar.pm does use Foo, doing use Foo elsewhere will start loading
Foo.pm, then hit the use statement, start loading Bar.pm, hit the use
statement, notice that Foo.pm has already started loading and ignore it,
and continue loading Bar.pm. But Foo.pm hasn't finished loading yet, so if
Bar.pm uses anything from Foo.pm (which it likely does, if it's loading it),
those won't be accessible while the body of Bar.pm is being executed. This
can lead to some very confusing errors, especially if introspection is
happening at load time (make_immutable in Moose classes, for example). This
module generates a warning whenever a module is skipped due to being loaded,
if that module has not finished executing.
This module works as a pragma, and typically pragmas have lexical scope.
Lexical scope doesn't make a whole lot of sense for this case though,
because the effect it's tracking isn't lexical (what does it mean to disable
the pragma inside of a cycle vs. outside of a cycle? does disabling it
within a cycle cause it to always be disabled for that cycle, or only if
it's disabled at the point where the warning would otherwise be generated?
etc.), but dynamic scope (the scope that, for instance, local uses) does,
and that's how this module works. Saying no circular::require enables the
module for the current dynamic scope, and use circular::require disables
it for the current dynamic scope. Hopefully, this will just do what you mean.
devel/p5-Package-Stash from 0.33nb2 to 0.34.
pkgsrc changes:
- adjusting dependencies
Upstream changes:
0.34 2013-01-04
- support anonymous stashes on newer perl versions
- prevent harmful effects from invalid settings for
$ENV{PACKAGE_STASH_IMPLEMENTATION}
- switch to Module::Implementation
devel/p5-Package-Stash-XS from 0.25nb2 to 0.26.
pkgsrc changes:
- adjust dependencies
Upstream changes:
0.26 2013-01-04
- internal refactorings to support Package::Anon stashes - this should
work now
------
0.6.46
------
* Issue #375: Issue a warning if the PYTHON_EGG_CACHE or otherwise
customized egg cache location specifies a directory that's group- or
world-writable.
into devel/p5-bareword-filehandles.
This module lexically disables the use of bareword filehandles with
builtin functions, except for the special builitin filehandles STDIN,
STDOUT, STDERR, ARGV, ARGVOUT and DATA.
into devel/p5-Test-Without-Module.
This module allows you to deliberately hide modules from a program even
though they are installed. This is mostly useful for testing modules
that have a fallback when a certain dependency module is not installed.
devel/p5-Devel-Hide.
Given a list of Perl modules/filenames, this module makes require and use
statements fail (no matter the specified files/modules are installed or
not).
They die with a message like:
Can't locate Module/ToHide.pm (hidden)
The intent of this module is to allow Perl developers to test for
alternative behavior when some modules are not available. In a Perl
installation, where many modules are already installed, there is a
chance to screw things up because you take for granted things that
may not be there in other machines.
devel/p5-Test-FailWarnings.
This module hooks $SIG{__WARN__} and converts warnings to Test::More's
fail() calls. It is designed to be used with done_testing, when you don't
need to know the test count in advance.
Just as with Test::NoWarnings, this does not catch warnings if other things
localize $SIG{__WARN__}, as this is designed to catch unhandled warnings.
devel/p5-Module-Build-Tiny.
Many Perl distributions use a Build.PL file instead of a Makefile.PL file to
drive distribution configuration, build, test and installation. Traditionally,
Build.PL uses Module::Build as the underlying build system. This module
provides a simple, lightweight, drop-in replacement.
Whereas Module::Build has over 6,700 lines of code; this module has less
than 120, yet supports the features needed by most distributions.
Supported
* Pure Perl distributions
* Building XS or C
* Recursive test files
* MYMETA
* Man page generation
* Generated code from PL files
Not Supported
* Dynamic prerequisites
* HTML documentation generation
* Extending Module::Build::Tiny
Directory structure
Your .pm and .pod files must be in lib/. Any executables must be in script/.
Test files must be in t/.
into devel/p5-ExtUtils-InstallPaths.
This module tries to make install path resolution as easy as possible.
When one wants to install a module, it needs to figure out where to install
things. The nutshell version of how this works is that default installation
locations are determined from ExtUtils::Config, and they may be individually
overridden by using the install_path attribute. An install_base attribute
lets one specify an alternative installation root like /home/foo and prefix
does something similar in a rather different (and more complicated) way.
destdir lets one specify a temporary installation directory like /tmp/install
in case one want to create bundled-up installable packages.
devel/p5-Carp-Always.
This module is meant as a debugging aid. It can be used to make a script
complain loudly with stack backtraces when warn()ing or die()ing.
from 2.35nb1 to 2.40.
pkgsrc changes:
- adjust license
- adjust dependencies
Upstream changes:
2.40 2013-07-01
- Added a conflict entry for older Log::Dispatch::File::Stamped to the
metadata. Patch by Karen Etheridge.
2.39 2013-04-21
- You can now pass a port option to the MailSender output. Patch by Whitney
Jackson.
2.38 2013-04-14
- Fix test that used undeclared prereqs so it does not do that.
2.37 2013-04-14
- Moved Log::Dispatch::File constructor parameter validation moved to
_basic_init() to facilitate proper subclassing. Patch by ether. RT #84545.
2.36 2013-04-08
- Added a very simple Log::Dispatch::Code output. This lets you log to a
subroutine reference.
- Added Sys::Syslog 0.25 as a prereq. This is a temporary fix to the problem
of Log::Dispatch shipping lots of output modules with undeclared prereqs (so
as not to require mod_perl, four email sending modules, etc.). In the future
Log::Dispatch will be split into a core distro and a set of distros, one for
each output that has prereqs. Reported by Michael Schwern. RT #84481.
to allow package to continue to work as previously packaged. +LICENSE;
From NEWS:
tig-1.1
-------
Incompatibilities:
- Disable diff move/copy detection by default, boosting diff
performance on larger projects. Use git config 'diff.renames' option
(git-wide) to set your preferred behavior. Environment variable
TIG_DIFF_OPTS can be used to restore the old behavior.
- Values set for author-width and filename-width will result in widths
one character bigger than previously.
Improvements:
- Typing a text in the prompt will be interpreted as a tig command.
Prefixing the command with a '!' will execute this system command in
an external pager. Entering a single key will execute the
corresponding key binding.
- Basic support for wrapping long line in pager, diff, and stage views.
Enable using: `set wrap-lines = yes`. (GH #2)
- User-defined commands prefixed with a '?' means prompt before
execution. Example: `bind main B !?git rebase -i %(commit)`.
- User-defined commands prefixed with a '<' means exit after execution.
Example: `bind main C !<git commit`. (GH #66)
- User-defined commands are executed unquoted to support shell commands.
Example: `bind generic I !@sh -c "echo -n %(commit) | xclip -selection c"`.
(GH #65)
- Configure case-insensitive searches using: `set ignore-case = yes`.
- Add "deleted mode" line type for better diff coloring.
- Open editor when requesting edit action from within a file diff.
- Update AX_WITH_CURSES to build under Cygwin.
- Improve tigrc(5) documentation. (Debian #682766)
- Allow to build on Mac OS 10.7 without the configure script. (GH #25)
- Add option to split the view vertically instead of horizontally.
Example: `set vertical-split = yes'. (GH #76)
- Add 'show-id' and 'id-width' options to configure the display of
commit IDs in the main view and ID width in the blame view. (GH #77)
- Allow to override git-based encoding to UTF-8 by setting
'i18n.commitencoding' or 'gui.encoding'.
- Improve autobuild support to track generated files and work with
autoreconf 2.61.
- Commit IDs are read from stdin when --stdin is given; works for main
and diff view, e.g. `tig --no-walk --stdin < cherry-picks.txt`.
- Add option to disable focusing of the child view when it's opened.
Disable using: `set focus-child = no`. (GH #83)
- Allow to open blob related with added content in a diff. (GH #91)
Bug fixes:
- Fix commit graph regression when a path spec is specified. (GH #53)
- Main view: only show staged/unstaged changes for the current branch.
- Support submodules created with current version of git. (GH #54)
- Fix diff status message for file diffs with no content changes.
- Fix parent blaming when tig is launched in subdirectory. (GH #70)
- Do not show deleted branch when reloading the branch view.
tig-1.0
-------
The master repository is git://github.com/jonas/tig.git, and the old
master repository (http://jonas.nitro.dk/tig/tig.git) will be retired.
Improvements:
- Use git-log(1)s default commit ordering. The old behavior can be
restored by adding `set commit-order = topo` to ~/.tigrc.
- Support staging of single lines. Bound to '1' default. (GH #21)
- Use +<lineno> to open the initial view at an arbitrary line. (GH #20)
- Add show-notes ~/.tigrc option. Notes are displayed by default.
- Support jumping to specific SHAs in the main view.
- Decorate replaced commits.
- Display line numbers in main view.
- Colorize binary diff stats. (GH #17)
- Custom colorization of lines matching a string prefix (GH #16).
Example configuration: color "Reported-by:" green default
- Use git's color settings for the main, status and diff views.
Put `set read-git-colors = no` in ~/.tigrc to disable.
- Handle editor options with multiple arguments. (GH #12)
- Show filename when running tig blame with copy detection. (GH #19)
- Use 'source <path>' command to load additional files from ~/.tigrc
- User-defined commands prefixed with '@' are run with no console
output, e.g.
bind generic 3 !@rm sys$command
- Make display of space changes togglable in the diff and stage view.
Bound to 'W' by default.
- Use per-file encoding specified in gitattributes(5) for blobs and
unstaged files.
- Obsolete commit-encoding option and pass --encoding=UTF-8 to revision
commands.
- Main view: show uncommitted changes as staged/unstaged commits.
Can be disabled by putting `set show-changes = no` in ~/.tigrc.
- Add %(prompt) external command variable, which will prompt for the
argument value.
- Log information about git commands when the TIG_TRACE environment
variable is set. Example: `TIG_TRACE=/tmp/tig.log tig`
- Branch view: Show the title of the last commit.
- Increase the author auto-abbreviation threshold to 10. (GH #49)
- For old commits show number of years in relative dates. (GH #50)
Bug fixes:
- Fix navigation behavior when going from branch to main view. (GH #38)
- Fix segfault when sorting the tree view by author name.
- Fix diff stat navigation for unmodified files with stat changes.
- Show branches/refs which names are a substring of the current branch.
- Stage view: fix off-by-one error when jumping to a file in a diff
with only one file.
- Fix diff-header colorization. (GH #15)
tig-0.18
--------
Incompatibilities:
- Remove support for the deprecated TIG_{MAIN,DIFF,LOG,TREE,BLOB}_CMD
environment variables.
Improvements:
- Pressing enter on diff stat file lines will jump to file's diff.
- Naïvely color blame IDs to distinguish lines.
- Document palette color options used for revision graph and blame IDs.
- Add support for blaming diff lines.
- Add diff-context option and bindings to increase the diff context in
the diff and stage view.
- (GH-6) Make blame configurable via extra options passed from the command
line and blame-options setting from ~/.tigrc. For example:
set blame-options = -C -C -C
Bug fixes:
- Expand browsing state variables for prompt. (LP #694780, Debian #635546)
- Fix segfault when sorting the branch view by author.
- Expand %(directory) to . for the root directory. (GH-3)
- Accept 'utf-8' for the line-graphics option as indicated in the docs.
- Use erasechar() to check for the correct backspace character.
Upstream changes:
1.306 Tue Jul 2 2013
[DOCUMENTATION]
- document how to run git from cwd in Git::Repository::Tutorial
(follow-up of RT #86154, thanks to Daniel B. Boorstein (DANBOO))
- document how to avoid the translation of Git messages by using
LC_ALL=C in Git::Repository::Tutorial
[TESTS]
- made tests more robust no matter which locale is defined
(thanks to Lars Dieckow (DAXIM))
1.305 Sun Jun 16 2013
[DOCUMENTATION]
- list the 'fatal' option in the documentation for run()
[TESTS]
- various fixes for t/24-errors.t
(mostly for Win32, thanks to Christian Walde (MITHALDU))
1.304 Sat May 25 2013
[ENHANCEMENTS]
- the new 'fatal' option makes it possible to define in detail
which exit status codes will make run() die, in addition to
the defaults 128 and 129 (many thanks to Grant McLean for
a great discussion about this, which inspired the feature)
[DOCUMENTATION]
- add a section about 'fatal' in Git::Repository::Tutorial
[TESTS]
- let Dist::Zilla manage the author tests
- fixed tests with older gits, and also moved requirements
for some tests a little bit further in the past
- tested against 326 versions of git (including all RC),
from 1.5.0.rc0 to 1.8.3.rc3
1.303 Sun Apr 28 2013
[ENHANCEMENTS]
- now depends on System::Command 1.100 for proper Win32 support
- thanks to a lot of testing help from Christian Walde (MITHALDU)
the test suite passes on Win32 (by skipping tests of little
importance)
Upstream changes:
1.100 Sun Apr 14 2013
[ENHANCEMENTS]
- use a IPC::Run-based implementation on Win32
- thanks to a lot of testing help from Christian Walde (MITHALDU)
the test suite passes on Win32
- while working on this, we established that kill 0, $pid is broken
under Win32 (reported to the perl5-porters mailing-list via
<op.wvi2ygw1ydyjqt@digitizedsqueak.lancs.ac.uk>)
1.09 Sun Dec 9 2012
[ENHANCEMENTS]
- list all dependencies and the github public repo in the META files
(RT #81302)
- use Symbol::gensym to create anonumous GLOBs (github #4)
1.08 Mon Nov 26 2012
[ENHANCEMENTS]
- remove a superfluous eval {} that was hiding open3 exception
(RT #80171)
- set a handler for the PIPE signal only if Perl knows about it
Upstream changes since 1.0:
log4cplus 1.1.1
- FileAppender - Accept also std::ios_base::ate as "append to a log
file" specification.
log4cplus 1.1.1-RC4
- Fixed bug #156 - Messages are truncated when produced using the
LOG4CPLUS_*_FMT() macros.
- Fixed bug #157 - Fedora package build failure.
- Improved log4cplus initialization:
- Use APC to initialize log4cplus outside loader lock.
- Use Microsoft C runtime library TLS callbacks to initialize
log4cplus as static library.
- Warn during compilation that automatic initialization is not
possible when log4cplus is being compiled with static Microsoft C
runtime library.
- Provide log4cplus::initialize() function to allow users to
initialize log4cplus in situations where automatic initialization
is not possible.
- Several improvements to CMake build:
- Fixed OpenBSD + CMake builds.
- Fixed issues with Visual Studio 2005 CMake builds.
- Added support for CMake builds on Android with NDK. (Sergey
Nikulov)
- The defines.hxx.cmake file is now generated out of defines.hxx.in.
- Library version is parsed out of version.h. (Sergey Nikulov)
- MDC formatter for PatternLayout ("%X") now expands into list of key
value pairs if no specific key is given. (Yaqian Shen)
- Avoid clock_nanosleep() on Android.
- ServerSocket::accept() can now be interrupted from another thread
using new function ServerSocket::interruptAccept().
log4cplus 1.1.1-RC3
- Fixed another MinGW related build failure.
- Fixed mismatched #if/#endif in Windows builds.
log4cplus 1.1.1-RC2
- Allow to disable TLS usage in macros through
LOG4CPLUS_MACRO_DISABLE_TLS preprocessor symbol.
- Fixed compilation with Clang on Cygwin.
- Fixed SIGSEGV when built with some MinGW distributions.
- Fixed build failure when using -march=i386.
- Implemented thread callback to initialize log4cplus for Visual
Studio builds of static library.
- Fixed bug #154 - getHostname() failure because of uninitialized
WinSock.
- Fixed detection of C++11 thread_local keyword.
- Fixed builds using DevKit-tdm-32-4.5.2-20111229-1559.
log4cplus 1.1.1-RC1
- Improved documentation for various classes.
- Cherry-picked various small improvements from trunk.
- Fixed Unicode builds on *NIX.
- Fixed static library builds from Visual Studio project.
- Suppressed warning C4127 from MSVC. (Chris Steenwyk)
- Improved MinGW32 and MinGW64 toolchains compatiblity.
- Fixed encoding handling in Properties class.
- Added include directive for properties files. (Jukka Lantto)
- Added colored output for Win32ConsoleAppender. (Konstantin Baumann)
- (Re)Introduced support for C++Builder (XE3)
- Reimplemented acceptSocket() using select() on Windows to allow
interrupting the accept() call from different thread.
log4cplus 1.1.0
- Fixed MacOS X support - Reimplemented semaphores using named ones
for Apple builds.
- Fixed resource leak on failure in openSocket().
- Improved configuration file modification check to include file size,
in addition to file modification time.
log4cplus 1.1.0-RC10
- Fixed non-STLPort4 builds with Solaris Studio. Switch
'-library=stlport4' is only added if CXXFLAGS does not already
contain a switch matching -library=(stlport4|stdcxx4|Cstd).
- Fixed --disable-shared MinGW builds.
- Fixed non-working MinGW DLL binaries. DllMain() was not being called
because of missing extern "C" in its definition.
- CMake build configuration checks have been improved. (Chernyshev
Vyacheslav)
- GCC switch -O2 is only added if CXXFLAGS does not already contain
any other -O.
- Improved logging speed using SysLogAppender and Log4jUdpAppender by
optimizations in both the loggers and in common sockets code.
- FileAppender locale can now be specified in properties files using
Locale property. See FileAppender Doxygen documentation for more
details.
log4cplus 1.1.0-RC9
- Improved Log4jUdpAppender compatibility with Chainsaw.
- Fixed crash, bugs #3467112 and #3563699, related to thread-local
storage destruction.
- Fixed build with Visual Studio 2005, bug #3565529. (xg00)
- Created Cygwin port's .cygport definition for log4cplus.
- Improved hiding of private symbols using GCC's
__attribute__((visibility("hidden"))) and Solaris Studio's __hidden.
- Fixed build in environments where DEBUG (and other log level names)
are macros. (Chernyshev Vyacheslav)
- Improved configuration of threads support. (Jens Rehsack)
log4cplus 1.1.0-RC8
- Turned on __thread (TLS) detection on NetBSD 5.1.0 and later that
has been previously disabled.
- Improved compatibility with log4cplus 1.0.x: allow using log4cplus
1.0.x log level to string callbacks in 1.1.x.
- Improved various M4 macros.
- Added detection and use C++11 thread_local.
- Fixed XML entities escaping in Log4jUdpAppender.
- Re-added synchronization between ConsoleAppender and LogLog.
- Changed C logger API to return int instead of bool.
- Added C logger API to Visual Studio 2010 projects.
- Implemented remote syslog logging using UDP in SysLogAppender.
- Enabled SysLogAppender on Windows with only remote syslog logging
enabled.
log4cplus 1.1.0-RC7
IMPORTANT: Builds with --with-iconv configure switch now assume UTF-8
for plain char strings.
- Bumped up SO version for UDP sockets support related changes.
- Removed Windows CE support.
- Regenerated with Automake 1.12.2.
- Fixed Fedora RPM builds spec file.
- Implemented log4cplus.disableOverride similar to log4j's
log4j.disableOverride.
- Improved support of profiling and debugging builds with Sun CC.
- Added documentation for configure script options.
- Added detection and use of clock_nanosleep().
- Disabled __thread (TLS) detection for NetBSD. It is broken there.
- New appender: Log4jUdpAppender. It allows logging using UDP with
log4j XML payload to Chainsaw or Log2Console. (Siva Chandran P)
- Added support for __func__ as function name source for logging
events.
log4cplus 1.1.0-RC6
- Fixed compilation for build with wchar_t being alias to unsigned
short (/Zc:wchar_t-) (Windows).
- Added new appender CLFSAppender (experimental), based on Microsoft
Common Log File System API.
- Added new appender Qt4DebugAppender (experimenta), based on Qt4's
qDebug(), qWarning() and qCritical() functions.
- Fixed bug #3530769 - compilation issues with Visual Studio 2011.
- Added log4cplus.quietMode property handling to PropertyConfigurator.
- Added #pragma once to all headers.
- Implemented Time::gettimeofday() using Win32 API's
GetSystemTimeAsFileTime().
- Moved file based locking from FileAppender to Appender to make it
available for all appenders.
- Changed Windows configuration to use __declspec(thread) when
compiling for Windows Vista or later and TlsAlloc() otherwise.
- Implemented %r PatternLayout format specifier - miliseconds since
process start.
- Fixed bug #3101459 - TTCCLayout time is not in milliseconds since
process start by default.
log4cplus 1.1.0-RC5
- Fixed single threaded log4cplus build issues.
- Added ability to log to std::cerr (Andreas Bießmann).
- Fixed disabling of LOG4CPLUS_*_FMT() macros.
log4cplus 1.1.0-RC4
IMPORTANT: Compilation with Solaris Studio now depends on STLPort
(-library=stlport4 switch). The default Cstd library is not
conforming enough for use in log4cplus.
- Improved behaviour of log4cplus as a component of larger CMake based
project (Andreas Bießmann).
- Updated various Autoconf detection scripts in m4/ directory to newer
versions.
- Fixed some signedness and overflow warnings.
- Improved Autotools build system's behaviour for cross compilation.
- Added detection of C++11 <atomic> header and related
functions. Implemented SharedObject reference counting using C++11
atomics where possible.
- Fixed compilation with GCC 4.6 in C++11 mode.
- Fixed some single-threaded compilation and run time issues.
- Fixed bug #3520891 - FileAppender buffering issue.
- Updated to Autoconf 2.69, Automake 1.12 and Libtool 2.4.2.
- Documented build procedure for Solaris Studio.
- Improved support for Solaris Studio in configure.in.
log4cplus 1.1.0-RC3
- Fixed log4cplusS.vcxproj - Added missing source files to the
project.
log4cplus 1.1.0-RC2
- CMake build system fixes.
- Fixed TTCCLayout double time stamp issue.
log4cplus 1.1.0-RC1
Important changes relative to PRODUCTION_1_0_x branch:
- Added AsyncAppender.
- Added simple C interface for interoperability with C.
- Added inter-process file locking to file appenders to allow logging
into a single log file from multiple processes.
- Added Mapped Diagnostic Context (MDC) and associated converter (%X).
- Added alternative thread identification (%T) converter to pattern layout.
- Added function name converter (%M).
- Added wchar_t <-> char conversion implementations based on standard
C locale functions and based on iconv().
- Added DeviceAppender to allow use of Boost.IOStream's Sink as appender.
- Added LOG4CPLUS_*_FMT() macros to allow printf-like formatted output
where it is possible.
- Logging macros now accept both logger name as string and Logger
instance as their first parameter.
* WARNING: New versioning scheme for Automake.
- Beginning with the release 1.13.2, Automake has started to use a
more rational versioning scheme, that should allow users to know
which kind of changes can be expected from a new version, based
on its version number.
+ Micro releases (e.g., 1.13.3, 2.0.1, 3.2.8) introduce only bug
and regression fixes and documentation updates; they should not
introduce new features, nor any backward-incompatibility (any
such incompatibility would be considered a bug, to be fixed with
a further micro release).
+ Minor releases (e.g., 1.14, 2.1) can introduce new backward
compatible features; the only backward-incompatibilities allowed
in such a release are new *non-fatal* deprecations and warnings,
and possibly fixes for old or non-trivial bugs (or even inefficient
behaviours) that could unfortunately have been seen and used by
some as "corner case features". Possible disruptions caused by
this kind of fixes should hopefully be quite rare, and their
effects limited in scope.
+ Major versions (now expected to be released every 18 or 24 months,
and not more often) can introduce new big features (possibly with
rough edges and not-fully-stabilized APIs), removal of deprecated
features, backward-incompatible changes of behaviour, and possibly
major refactorings (that, while ideally transparent to the user,
could introduce new bugs). Incompatibilities should however not
be introduced gratuitously and abruptly; a proper deprecation path
should be duly implemented in the preceding minor releases.
- According to this new scheme, the next major version of Automake
(the one that had previously been labelled as "1.14") will actually
become "Automake 2.0". Automake 1.14 is *this* release (which is
a minor one). It introduces new features, deprecations and bug
fixes, but no serious backward incompatibility. A partial exception
is given by the behavioural changes in the AM_PROG_CC_C_O macro
(described in details below) but such changes can also be seen as a
fix for the old suboptimal and somewhat confusing behaviour.
- See discussion about automake bug#13578 for more details and
background: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13578>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* WARNING: Future backward-incompatibilities!
- Makefile recipes generated by Automake 2.0 will expect to use an
'rm' program that doesn't complain when called without any non-option
argument if the '-f' option is given (so that commands like "rm -f"
and "rm -rf" will act as a no-op, instead of raising usage errors).
This behavior of 'rm' is very widespread in the wild, and it will be
required in the next POSIX version:
<http://austingroupbugs.net/view.php?id=542>
Accordingly, AM_INIT_AUTOMAKE now expands some shell code that checks
that the default 'rm' program in PATH satisfies this requirement,
aborting the configure process if this is not the case. For the
moment, it's still possible to force the configuration process to
succeed even with a broken 'rm', that that will no longer be the case
for Automake 2.0.
- Automake 2.0 will require Autoconf 2.70 or later (which is still
unreleased at the moment of writing, but is planned to be released
before Automake 2.0 is).
- Automake 2.0 will drop support for the long-deprecated 'configure.in'
name for the Autoconf input file. You are advised to start using the
recommended name 'configure.ac' instead, ASAP.
- The ACLOCAL_AMFLAGS special make variable will be fully deprecated in
Automake 2.0: it will raise warnings in the "obsolete" category (but
still no hard error of course, for compatibilities with the many, many
packages that still relies on that variable). You are advised to
start relying on the new Automake support for AC_CONFIG_MACRO_DIRS
instead (which was introduced in Automake 1.13).
- Automake 2.0 will remove support for automatic dependency tracking
with the SGI C/C++ compilers on IRIX. The SGI depmode has been
reported broken "in the wild" already, and we don't think investing
time in debugging and fixing is worthwhile, especially considering
that SGI has last updated those compilers in 2006, and is expected
to retire support for them in December 2013:
<http://www.sgi.com/services/support/irix_mips_support.html>
- Automake 2.0 will remove support for MS-DOS and Windows 95/98/ME
(support for them was offered by relying on the DJGPP project).
Note however that both Cygwin and MSYS/MinGW on modern Windows
versions will continue to be fully supported.
- Automake-provided scripts and makefile recipes might (finally!)
start assuming a POSIX shell in Automake 2.0. There still is no
certainty about this though: we'd first like to wait and see
whether future Autoconf versions will be enhanced to guarantee
that such a shell is always found and provided by the checks in
./configure.
- Starting from Automake 2.0, third-party m4 files located in the
system-wide aclocal directory, as well as in any directory listed
in the ACLOCAL_PATH environment variable, will take precedence
over "built-in" Automake macros. For example (assuming Automake
is installed in the /usr/local hierarchy), a definition of the
AM_PROG_VALAC macro found in '/usr/local/share/aclocal/my-vala.m4'
should take precedence over the same-named automake-provided macro
(defined in '/usr/local/share/aclocal-2.0/vala.m4').
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
New in 1.14:
* C compilation, and the AC_PROG_CC and AM_PROG_CC_C_O macros:
- The 'compile' script is now unconditionally required for all packages
that perform C compilation (if you are using the '--add-missing'
option, automake will fetch that script for you, so you shouldn't
need any explicit adjustment). This new behaviour is needed to avoid
obscure errors when the 'subdir-objects' option is used, and the
compiler is an inferior one that doesn't grasp the combined use of
both the "-c -o" options; see discussion about automake bug#13378 for
more details:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#35>
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13378#44>
- The next major Automake version (2.0) will unconditionally activate
the 'subdir-objects' option. In order to smooth out the transition,
we now give a warning (in the category 'unsupported') whenever a
source file is present in a subdirectory but the 'subdir-object' is
not enabled. For example, the following usage will trigger such a
warning:
bin_PROGRAMS = sub/foo
sub_foo_SOURCES = sub/main.c sub/bar.c
- Automake will automatically enhance the autoconf-provided macro
AC_PROG_CC to force it to check, at configure time, that the
C compiler supports the combined use of both the '-c' and '-o'
options. The result of this check is saved in the cache variable
'am_cv_prog_cc_c_o', and said result can be overridden by
pre-defining that variable.
- The AM_PROG_CC_C_O macro can still be called, albeit that should no
longer be necessary. This macro is now just a thin wrapper around the
Automake-enhanced AC_PROG_CC. This means, among the other things,
that its behaviour is changed in three ways:
1. It no longer invokes the Autoconf-provided AC_PROG_CC_C_O
macro behind the scenes.
2. It caches the check result in the 'am_cv_prog_cc_c_o' variable,
and not in a 'ac_cv_prog_cc_*_c_o' variable whose exact name is
dynamically computed only at configure runtime (really!) from
the content of the '$CC' variable.
3. It no longer automatically AC_DEFINE the C preprocessor
symbol 'NO_MINUS_C_MINUS_O'.
* Texinfo support:
- Automake can now be instructed to place '.info' files generated from
Texinfo input in the builddir rather than in the srcdir; this is done
specifying the new automake option 'info-in-builddir'. This feature
was requested by the developers of GCC, GDB, GNU binutils and the GNU
bfd library. See the extensive discussion about automake bug#11034
for more details.
- For quite a long time, Automake has been implementing an undocumented
hack which ensured that '.info' files which appeared to be cleaned
(by being listed in the CLEANFILES or DISTCLEANFILES variables) were
built in the builddir rather than in the srcdir; this hack was
introduced to ensure better backward-compatibility with package
such as Texinfo, which do things like:
info_TEXINFOS = texinfo.txi info-stnd.texi info.texi
DISTCLEANFILES = texinfo texinfo-* info*.info*
# Do not create info files for distribution.
dist-info:
@:
in order not to distribute generated '.info' files.
Now that we have the 'info-in-builddir' option that explicitly causes
generated '.info' files to be placed in the builddir, this hack should
be longer necessary, so we deprecate it with runtime warnings. It will
likely be removed altogether in Automake 2.0.
* Relative directory in Makefile fragments:
- The special Automake-time substitutions '%reldir%' and '%canon_reldir%'
(and their short versions, '%D%' and '%C%' respectively) can now be used
in an included Makefile fragment. The former is substituted with the
relative directory of the included fragment (compared to the top-level
including Makefile), and the latter with the canonicalized version of
the same relative directory.
# in 'Makefile.am':
bin_PROGRAMS = # will be updated by included Makefile fragments
include src/Makefile.inc
# in 'src/Makefile.inc':
bin_PROGRAMS += %reldir%/foo
%canon_reldir%_foo_SOURCES = %reldir%/bar.c
This should be especially useful for packages using a non-recursive
build system.
* Deprecated distribution formats:
- The 'shar' and 'compress' distribution formats are deprecated, and
scheduled for removal in Automake 2.0. Accordingly, the use of the
'dist-shar' and 'dist-tarZ' will cause warnings at automake runtime
(in the 'obsolete' category), and the recipes of the Automake-generated
targets 'dist-shar' and 'dist-tarZ' will unconditionally display
(non-fatal) warnings at make runtime.
* New configure runtime warnings about "rm -f" support:
- To simplify transition to Automake 2.0, the shell code expanded by
AM_INIT_AUTOMAKE now checks (at configure runtime) that the default
'rm' program in PATH doesn't complain when called without any
non-option argument if the '-f' option is given (so that commands like
"rm -f" and "rm -rf" act as a no-op, instead of raising usage errors).
If this is not the case, the configure script is aborted, to call the
attention of the user on the issue, and invite him to fix his PATH.
The checked 'rm' behavior is very widespread in the wild, and will be
required by future POSIX versions:
<http://austingroupbugs.net/view.php?id=542>
The user can still force the configure process to complete even in the
presence of a broken 'rm' by defining the ACCEPT_INFERIOR_RM_PROGRAM
environment variable to "yes". And the generated Makefiles should
still work correctly even when such broken 'rm' is used. But note
that this will no longer be the case with Automake 2.0 though, so, if
you encounter the warning, please report it to us ASAP (and try to fix
your environment as well).
This is a regularly-scheduled bugfix release.
commit: amending with --close-branch (issue3445)
doc: make it easier to read how to enable extensions
doc: reword "config file" to "configuration file"
docs: change description to synopsis in hgrc.5
histedit: raise ImportError when demandloading is enabled
pathencode: fix hashmangle short dir limit (issue3958)
update: remove .hg/graftstate on clean (issue3970)
Commented patches, Buildlink'd protobuf, libinotify, startup-notification,
libxslt, libSM, libICE, libXrandr, and libX11 in Makefile. Added protobuf
and libX11 to buildlink3.mk.
Changelog:
MantisBT 1.2.15 is a security update for the stable 1.2.x branch. All installations that are currently running any 1.2.x version are strongly advised to upgrade to this release.
- 0002971: [bugtracker] Reminders are not added to bug history (dregad) - closed.
- 0015470: [bugtracker] Reminders recipient list is truncated (dregad) - closed.
- 0010047: [documentation] Adding new statuses section is missing a step (dregad) - closed.
- 0010118: [documentation] lang_get_current() returns wrong language if $g_default_language overwritten (dregad) - closed.
- 0010372: [feature] Don't allow reminders to be sent if the user doesn't have an email address specificed (dregad) - closed.
- 0013054: [installation] Installer displays a blank page if core.php encounters a critical error (dregad) - closed.
- 0015357: [bugtracker] uninitialized library path (dregad) - closed.
- 0015471: [bugtracker] bug_reminder.php does not handle unsent reminders (dregad) - closed.
- 0015472: [bugtracker] email_bug_reminder() API's return array is always full list of recipients (dregad) - closed.
- 0015481: [custom fields] Custom fields values are not sorted in the main filter (dregad) - closed.
- 0015528: [printing] Custom fields user has no access to should not be displayed on print pages (dregad) - closed.
- 0015538: [bugtracker] Issues list is not displayed when $g_limit_reporters is ON (dregad) - closed.
- 0015540: [documentation] Wrong example code for custom status translation (atrol) - closed.
- 0015558: [bugtracker] url_get() does not fall back to other methods when no data is retrieved (dregad) - closed.
- 0015573: [security] CVE-2013-1883: One query can be issued via current Mantis interface to take down site (dregad) - closed.
- 0015575: [documentation] Turning on $g_show_queries_list causes Mantis to crash with an error (dregad) - closed.
- 0015659: [localization] Appears @70@ and @80@ in the list of resolutions in the "view Issues" page when mantis is in catalan. (dregad) - closed.
- 0015691: [administration] Config report: retrieval of saved project filter from cookie does not work (dregad) - closed.
- 0015453: [security] CVE-2013-1930: Close button is shown on webpage despite 'close' is not a valid status by workflow (dregad) - closed.
- 0015511: [security] CVE-2013-1931: XSS vulnerability when deleting a version (atrol) - closed.
- 0015698: [bugtracker] 'extract() expects parameter 1 to be array, boolean given' in '/srv/www/bugs/account_prof_edit_page.php' line 48 (dregad) - closed.
- 0015704: [documentation] Wrong description of writing custom_functions (atrol) - closed.
- 0015744: [bugtracker] Reminder bugnote with list of recipients not added if no text provided (dregad) - closed.
- 0015451: [api soap] Incorrect invocations of SoapObjectsFactory::newSoapFault (rombert) - closed.
- 0015517: [api soap] mc_project_get_versions() result can't be parsed by C# (dregad) - closed.
- 0015522: [api soap] mc_project_get_issues does not report due_date (dregad) - closed.
MantisBT 1.2.14 is a security update for the stable 1.2.x branch. All installations that are currently running any 1.2.x version are strongly advised to upgrade to this release.
Please refer to the release notes for details.
- 0015416: [security] CVE-2013-1934: XSS issue in adm_config_report.php when displaying complex value (dregad) - closed.
- 0015415: [security] CVE-2013-1932: XSS vulnerability on Configuration Report page (dregad) - closed.
- 0015411: [performance] Huge memory consumption for print_user_option_list() (dregad) - closed.
MantisBT 1.2.13 had to be withdrawn shortly after release, as it introduced a bug
(#15411) causing the View Issues page to consume significantly more memory for
instances with large numbers of users (order 10k+), leading to system crashes,
as well as an XSS issue (#15415) in the Configuration Report page.
We recommend not to use 1.2.13, and deploy version 1.2.14 instead.
- 0014871: [api soap] Add support for the built-in soap extension in addition to nusoap (rombert) - closed.
- 0003693: [bugtracker] Make the username in Manage Projects a clickable link to edit that user (dregad) - closed.
- 0007586: [customization] generic configuration editor cannot 'EDIT' an option (dregad) - closed.
- 0010130: [filters] Filter "Assigned to" does not display usernames when project "All Projects" is selected (dregad) - closed.
- 0011854: [documentation] Parameter $g_default_timezone" is not mentioned in administration_guide (dregad) - closed.
- 0013298: [preferences] commas and multi-dimensional arrays in adm_config_set (dregad) - closed.
- 0013680: [performance] Configuration page takes a very long time to load (dregad) - closed.
- 0014009: [administration] admin/check.php fatal error on PHP 5.1.x (undefined function timezone_identifiers_list()) (dregad) - closed.
- 0014559: [administration] Adding filter for "Configuration report" (dregad) - closed.
- 0015199: [other] Update json api error format (rombert) - closed.
- 0015201: [db postgresql] Summary page fail (dregad) - closed.
- 0015384: [security] CVE-2013-1810 XSS vulnerability on summary page (dhx) - closed.
- 0015247: [administration] Protected account change still sends email (dregad) - closed.
- 0015248: [email] The order of sending emails is inverted when using cron (dregad) - closed.
- 0015255: [bugtracker] Date filter fields are disabled when $g_use_javascript = OFF (dregad) - closed.
- 0015257: [filters] Inconsistent use of numeric vs text month in date filter selection fields (dregad) - closed.
- 0015258: [security] CVE-2013-1811 Reporter can change issue status to 'new' (dregad) - closed.
- 0015260: [bugtracker] access_get_status_threshold() returns incorrect value for NEW (dregad) - closed.
- 0015264: [custom fields] custom_field_get_id_from_name() broken since 1.2.12 (dregad) - closed.
- 0015265: [custom fields] custom_field_get_id_from_name() doesn't cache result of obsolete custom field names (dregad) - closed.
- 0015280: [code cleanup] Form in manage_columns_inc.php has misleading name and unnecessary multipart encoding (dregad) - closed.
- 0015320: [filters] Date filters broken since 1.2.12 (rombert) - closed.
- 0015360: [bugtracker] Add Missing config 'reminder_receive_threshold' in workflow threshold page (dregad) - closed.
- 0015370: [bugtracker] When a bug is resolved on report, default the handler to the current user (rombert) - closed.
- 0015373: [security] CVE-2013-0197 XSS vulnerability with match_type filter (dhx) - closed.
- 0015382: [email] Additional improvements to email logging (dregad) - closed.
- 0015388: [filters] Update the match_type parameter to be XSS-safe by itself (dregad) - closed.
- 0015389: [filters] Display of match_type filter property for unknown types (dregad) - closed.
- 0015356: [api soap] improve error handling in mc_issue_api.php (rombert) - closed.
- 0014157: [api soap] Array to string conversion error on soap request with PHP 5.4 (rombert) - closed.
- 0014672: [api soap] Slow performance of SOAP calls due to nusuoap (rombert) - closed.
- 0015222: [api soap] mc_project_delete_category fails to delete category (rombert) - closed.
Changelog:
This is Version 1.26. Key changes in this release include:
The argument to the --port option for the "fossil ui" and "fossil server" commands can take an IP address in addition to the port number, causing Fossil to bind to just that one IP address.
After prompting for a password, also ask if that password should be remembered.
Performance improvements to the diff engine.
Fix the side-by-side diff engine to work better with multi-byte unicode text.
Color-coding in the web-based annotation (blame) display. Fix the annotation engine so that it is no longer confused by time-warps.
The markdown formatter is now available by default and can be used for tickets, wiki, and embedded documentation.
Add subcommands "fossil bisect log" and "fossil bisect status" to the "fossil bisect" command, as well as other bisect enhancements.
Enhanced defenses that prevent spiders from using excessive CPU and bandwidth.
Consistent use of the -n or --dry-run command line options.
Win32: Fossil now understands Cygwin paths containing one or more of the characters "*:<>?|. Those are normally forbidden in win32. This means that the win32 fossil.exe is better usable in a Cygwin environment.
Cygwin: Fossil now understands win32 absolute paths starting with a drive letter everywhere. The default value of the "case-sensitive" setting is now FALSE, except when case-sensitivity is enabled in the Windows kernel.
Enhancements to /timeline.rss, adding more flags for filtering results, including the ability to subscribe to changes made to individual tickets.
Improved handling of the differences between case-sensitive and case-insensitive filesystems.
JSON API: added the 'status' command to report local checkout status.
Fixes to the --args support and documented this feature in the help.
Added /stats_report page.
Added ym=YYYY-MM filter to the "/timeline" url.
Fixed: config reset now re-installs default ticket report format.
ssh:// and file:// protocols now ignore proxy settings.
Added /hash-color-test web page.
Cherry-pick merges are recorded internally (though no yet displayed on the timeline graph.)
Bring in the latest versions of SQLite, zlib, and autosetup from upstream.
PathTools in devel/p5-PathTools from 3.33nb3 to 3.40.
This is required, because Perl5 5.18.0 comes with PathTools 3.40 bundled
and some CPAN packages rely on this - pkgsrc installed PathTools 3.33
overrides core modules which is a downgrade and should have a sane
reason.
Upstream changes since 3.33:
3.40 - Wed Jan 16 07:30:00 2013
- Stop inadvertently skipping Spec.t on VMS. (Craig Berry)
- Rethink EFS in File::Spec::VMS. (Craig Berry)
- File::Spec::UNIX->abs2rel() gets it wrong with ".." components
[perl #111510] (Volker Schatz)
- Add C define to remove taint support from perl (Steffen Mueller)
- Remove "register" declarations as they are no longer
useful (Karl Williamson)
- Add test for fast_abs_path in LF dir
[perl #115962] (Father Chrysostomos)
- Cwd::fast_abs_path's untaint should allow for multiline
directories (Joel Berger)
3.39_01 - Tue Dec 20 08:30:00 2011
- [perl #51562] Problem & "solution" for building 5.10.0 with
win32+mingw+dmake (kmx)
- Fix various compiler warnings from XS code (Zefram)
- Fix typos (spelling errors) (Peter J. Acklam)
- Remove Mac OS classic only tests from Cwd's Spec.t
and special case code from Cwd's cwd.t (Nicholas Clark)
- Convert File::Spec's remaining tests to Test::More from Test
(Nicholas Clark)
- dist/Cwd/lib/File/Spec/Win32.pm: Fix broken link (Karl Williamson)
- In Cwd::_win32_cwd() avoid a string eval when checking if we're
miniperl (Nicholas Clark)
- Add PERL_NO_GET_CONTEXT to Cwd (Nicholas Clark)
- In Cwd.xs on VMS, don't compile bsd_realpath() at all (Nicholas Clark)
- Merge the implementation of Cwd::{fastcwd,getcwd} using
ALIAS (Nicholas Clark)
- In Cwd.xs, swap to defaulting to disabled prototypes (Nicholas Clark)
- Remove duplicate $VERSION handling code, made redundant
in 3.28_01 (Nicholas Clark)
- In Cwd.xs, tidy the conditional code related to symlinks
(Nicholas Clark)
- Keep verbatim pod within 80 cols (Father Chrysostomos)
- [RT #36079] Convert ` to ' in docs (Jim Keenan)
- [rt.cpan.org #45885] File::Spec: Don’t use tainted tmpdir
in 5.6 (Father Chrysostomos)
Try-Tiny-0.12 in devel/p5-Try-Tiny from 0.11nb2 to 0.12 because of
forced www/p5-Apache-LogFormat-Compiler update requires Try::Tiny 0.12.
Upstream changes:
0.12
- doc fixes
the static and tests options. PLIST is handled accordingly for the static
option, which switches between static and dynamically linked libraries.
Handle buildlink3.mk appropriately for static build. Comment patch.
From ChangeLog:
from ucommon 6.0.4 to 6.0.5
- additional constructors to pass pre-allocated memory
from ucommon 6.0.3 to 6.0.4
- fix for address list comparison issue
- fix configure scripts to detect !G_ATOMIC_LOCK_FREE correctly
(use AC_TRY_LINK rather than AC_TRY_COMPILE to see if symbols are defined)
- fix prototype mismatches in !G_ATOMIC_LOCK_FREE case
(note no binary changes in G_ATOMIC_LOCK_FREE case)
"please commit it" from agc@.
