Pkgsrc changes:
- adjust dependencies
Upstream changes:
1.05 Thu, May 20, 2010
[API CHANGES]
* Packages and modules no longer have methods - this functionality was
moved back up into Moose::Meta::Class and Moose::Meta::Role individually
(through the Class::MOP::Mixin::HasMethods mixin) (doy).
* BUILDALL is now called by Moose::Meta::Class::new_object, rather than by
Moose::Object::new. (doy)
[NEW FEATURES]
* strict and warnings are now unimported when Moose, Moose::Role, or
Moose::Exporter are unimported. (doy, Adam Kennedy)
* Added a 'consumers' method to Moose::Meta::Role for finding all
classes/roles which consume the given role. (doy)
[BUG FIXES]
* Fix has '+attr' in Roles to explode immediately, rather than when the role
is applied to a class (t0m).
* Fix type constraint validation messages to not include the string 'failed'
twice in the same sentance (Florian Ragwitz).
* New type constraints will default to being unequal, rather than equal
(rjbs).
* The tests no longer check for perl's behavior of clobbering $@, which has
been fixed in perl-5.13.1 (Florian Ragwitz).
* Metaclass compatibility fixing has been completely rewritten, and should
be much more robust. (doy)
1.04 Thu, May 20, 2010
* This release was broken and has been deleted from CPAN shortly after its
upload.
Pkgsrc changes:
- Adjust dependencies
Upstream changes:
1.02 Thu, May, 2010
[API CHANGES]
* Packages and modules no longer have methods - this functionality was
moved back up into Class::MOP::Class (doy).
[ENHANCEMENTS]
* Metaclass incompatibility checking now checks all metaclass types. (doy)
* Class::MOP can now do simple metaclass incompatibility fixing: if your
class's metaclass is a subclass of your parent class's metaclass, it will
just use the parent class's metaclass directly. (doy)
Upstream changes:
1.0004 Fri May 14 16:08:23 PDT 2010
- Do not use Cwd::abs_path if the -l path begins with / (rafl)
- Skipping perl should now be considered as success, not failure (rafl)
- Fixed PREREQ_PM scanner for dists that conflict with core functions such as UNIVERSAL::isa (yannk)
- --look should now imply --no-skip-installed (doy) #45
Upstream changes:
2.34 Thu Apr 20 2010
- Updated for 5.13.1
2.31_01 Fri Apr 30 2010
- [rt.cpan.org #56740] Format Perl versions >= 5.6.0 as X.Y.Z (schwern)
- Functional interface amended to make calling conventions consistent
(bingos)
- Documented all functions and all hash structures (bingos)
- Fixed functions with edge-case involving querying for Module::CoreList
itself. Pointed out by Ilmari.
- Added removed_from() and removed_from_by_date() functions
for querying which release a module was removed from core. (bingos)
- Amended corelist utility to use new removed from functions when
stating when a module entered core ( and when it left it ). (bingos)
- Added tests to the testsuite to cover the edge-cases and new funcs. (bingos)
Andrew's Web Libraries are a set of hopefully lightweight libraries for
handling a variety of useful things for web programming, including:
- Session management
- User management
- DB Records
- Simple reporting
- DB Schema Updating
- iCalendar parsing
Gio:
* MemoryInputStream: Correct data loss/corruption with binary data.
Glib:
* tests: Reorder assignment to LDADD and giomm_ldadd in tests/Makefile.am
to always use the built library, not the installed one.
Build:
* MSVC++ project fixes.
* Documentation:
- Added main page text with doxygen.
- Fix the functors Doxygen group.
- Tutorial: Removed outdated marshallers section that had no working example.
This module does not provide any methods. Simply loading it changes
the default naming policy for the loading class so that accessors
are separated into get and set methods. The get methods are prefixed
with "get_" as the accessor, while set methods are prefixed with
"set_". This is the naming style recommended by Damian Conway in
Perl Best Practices.
If you define an attribute with a leading underscore, then both the
get and set method will also have an underscore prefix.
If you explicitly set a "reader" or "writer" name when creating an
attribute, then that attribute's naming scheme is left unchanged.
Modern Perl programs use several modules to enable additional
features of Perl and of the CPAN. Instead of copying and pasting
all of these use lines, instead write only one:
use Modern::Perl;
This module implements a FIFO queueing infrastructure, using a
directory as the communications and storage media. No daemon process
is required to manage the queue; all communication takes place via
the filesystem.
New Libraries:
* Functional/factory: Function objects for dynamic and by-value construction.
* Functional/forward: Function object adapters to address the forwarding
problem.
Major Updates:
* Range: Boost.Range has undergone extensive updates that it include all of the
features from the recently reviewed Boost.RangeEx.
* Range-based version of the full STL iterator based algorithms.
* Range adaptors which can be combined with range-based algorithms for
unpresedented expressiveness and efficiency.
* New functions: irange, istream_range, join, combine.
Updated Libraries
Build System:
* When cross-compiling to GNU targets, static libraries are properly created.
Previously, using such libraries resulted in Archive has no index error.
* The naming of DLL and import libraries with gcc compiler on Windows, both
mingw and cygwin, now matches default conventions of those environments.
Previously, the naming scheme was the same as for other Windows compilers.
Updated Tools:
* Quickbook: Unicode escape characters.
* Support the UTF-8 byte order mark.
* Disallow [ in simple markup. Fixes some errors with mismatched punctuation.
* Add a command line flag (-D) to define macros at the command line.
* Improved post-processor output.
* Check that [section] and [endsect] tags are balanced in templates.
1.5.3 - 2010-05-13
This is an unscheduled bugfix release to fix Issue2181 (commit generates traceback on Nonetype). Also included:
* various improvements to SVN conversion support
* minor doc improvements
Pkgsrc changes:
- adjust dependencies
Upstream changes:
1.01 Thu, May 26, 2010
[NEW FEATURES]
* is_class_loaded, load_class and load_first_existing_class now allow
specifying a minimum required version (Florian Ragwitz).
[BUG FIXES]
* The __INSTANCE__ parameter to Class::MOP::Class::new_object now enforces
that the passed in reference is blessed into the correct class (by dying if
it's not) (doy, jhallock).
Numerous fixes in Konsole, KDE's terminal emulator, among them two possible
crashers in session management
Flash plugin support in KHTML has been enhanced to work with newest Youtube
skins
Case-sensitivity in renaming fixes in KIO, KDE's network-transparent I/O
library
Hiding the mouse cursor in some special cases in presentation mode and two
possible crashers have been fixed
Experimental version released on May 7th, 2010.
* Test programs no longer run several test cases in a row. The execution
of a test program now requires a test case name, and that single test
case is executed. To execute several test cases, use the atf-run
utility as usual.
* Test programs no longer fork a subprocess to isolate the execution of
test cases. They run the test case code in-process, and a crash of the
test case will result in a crash of the test program. This is to ease
debugging of faulty test cases.
* Test programs no longer isolate their test cases. This means that they
will not create temporary directories nor sanitize the environment any
more. Yes: running a test case that depends on system state by hand
will most likely yield different results depending on where (machine,
directory, user environment, etc.) it is run. Isolation has been moved
to atf-run.
* Test programs no longer print a cryptic format (application/X-atf-tcs)
on a special file channel. They can now print whatever they want on
the screen. Because test programs can now only run one test case every
time, providing controlled output is not necessary any more.
* Test programs no longer write their status into a special file
descriptor. Instead, they create a file with the results, which is
later parsed by atf-run. This changes the semantics of the -r flag.
* atf-run has been adjusted to perform the test case isolation. As a
result, there is now a single canonical place that implements the
isolation of test caes. In previous releases, the three language
bindings (C, C++ and shell) had to be kept in sync with each other
(read: not a nice thing to do at all). As a side effect of this
change, writing bindings for other languages will be much, much easier
from now on.
* atf-run forks test programs on a test case basis, instead of on a test
program basis as it did before. This is to provide the test case
isolation that was before implemented by the test programs themselves.
* Removed the atf-exec tool. This was used to implement test case
isolation in atf-sh, but it is now unnecessary.
* It is now optional to define the descr meta-data property. It has been
proven to be mostly useless, because test cases often carry a
descriptive name of their own.
Upstream changes:
1.02 Sat, May 01, 2010
[BUG FIXES]
* Stop the natatime method provided by the native Array trait from returning
an exhausted iterator when being called with a callback. (Florian Ragwitz)
* Make Moose::Meta::TypeConstraint::Class correctly reject RegexpRefs.
(Florian Ragwitz)
* Calling is_subtype_of on a Moose::Meta::TypeConstraint::Class with itself or
the class the TC represents as an argument incorrectly returned true. This
behavior is correct for is_type_of, not is_subtype_of. (Guillermo Roditi)
* Use File::Temp for temp files created during tests. Previously, files were
written to the t/ dir, which could cause problems of the user running the
tests did not have write access to that directory.. (Chris Weyl, Ævar
Arnfjörð Bjarmason)
* Pass role arguments along when applying roles to instances. (doy, lsm)
Upstream changes:
1.01 Thu 18 Mar 2010
- Fixed can_cc() bug in Makefile.PL where it was checking an existence
of PATH directory rather than executables. RT#55668 (DGOLDEN, MIYAGAWA)
2.2.6:
* Slight documentation changes.
(Murray Cumming) Bug #614741 (Armin Burgmeier)
2.2.5:
* Accumulators: Allow return types that are different to the signal's.
(Krzysztof Kosiński)
* Documentation:
- Disable collaboration graphs in documentation
- Use non-blurry font for graph labels.
(Daniel Elstner)
- sigc::hide() correction: It always only hides one signal argument.
(Michael Hasselmann)
* Fix the MSVC++ build.
(Armin Burgmeier)
* Changes in version 2.4.2 (2010-03-20):
** Some portability problems that resulted in failures and livelocks
in the test suite on some versions of at least Solaris, AIX, HP-UX,
RHEL4, and Tru64 have been addressed. As a result, fatal Bison
errors should no longer cause M4 to report a broken pipe on the
affected platforms.
** `%prec IDENTIFIER' requires IDENTIFIER to be defined separately.
POSIX specifies that an error be reported for any identifier that does
not appear on the LHS of a grammar rule and that is not defined by
%token, %left, %right, or %nonassoc. Bison 2.3b and later lost this
error report for the case when an identifier appears only after a
%prec directive. It is now restored. However, for backward
compatibility with recent Bison releases, it is only a warning for
now. In Bison 2.5 and later, it will return to being an error.
** Detection of GNU M4 1.4.6 or newer during configure is improved.
** Warnings from gcc's -Wundef option about undefined YYENABLE_NLS,
YYLTYPE_IS_TRIVIAL, and __STRICT_ANSI__ in C/C++ parsers are now
avoided.
** %code is now a permanent feature.
A traditional Yacc prologue directive is written in the form:
%{CODE%}
To provide a more flexible alternative, Bison 2.3b introduced the
%code directive with the following forms for C/C++:
%code {CODE}
%code requires {CODE}
%code provides {CODE}
%code top {CODE}
These forms are now considered permanent features of Bison. See the
%code entries in the section "Bison Declaration Summary" in the Bison
manual for a summary of their functionality. See the section
"Prologue Alternatives" for a detailed discussion including the
advantages of %code over the traditional Yacc prologue directive.
Bison's Java feature as a whole including its current usage of %code
is still considered experimental.
** YYFAIL is deprecated and will eventually be removed.
YYFAIL has existed for many years as an undocumented feature of
deterministic parsers in C generated by Bison. Previously, it was
documented for Bison's experimental Java parsers. YYFAIL is no longer
documented for Java parsers and is formally deprecated in both cases.
Users are strongly encouraged to migrate to YYERROR, which is
specified by POSIX.
Like YYERROR, you can invoke YYFAIL from a semantic action in order to
induce a syntax error. The most obvious difference from YYERROR is
that YYFAIL will automatically invoke yyerror to report the syntax
error so that you don't have to. However, there are several other
subtle differences between YYERROR and YYFAIL, and YYFAIL suffers from
inherent flaws when %error-verbose or `#define YYERROR_VERBOSE' is
used. For a more detailed discussion, see:
http://lists.gnu.org/archive/html/bison-patches/2009-12/msg00024.html
The upcoming Bison 2.5 will remove YYFAIL from Java parsers, but
deterministic parsers in C will continue to implement it. However,
because YYFAIL is already flawed, it seems futile to try to make new
Bison features compatible with it. Thus, during parser generation,
Bison 2.5 will produce a warning whenever it discovers YYFAIL in a
rule action. In a later release, YYFAIL will be disabled for
%error-verbose and `#define YYERROR_VERBOSE'. Eventually, YYFAIL will
be removed altogether.
There exists at least one case where Bison 2.5's YYFAIL warning will
be a false positive. Some projects add phony uses of YYFAIL and other
Bison-defined macros for the sole purpose of suppressing C
preprocessor warnings (from GCC cpp's -Wunused-macros, for example).
To avoid Bison's future warning, such YYFAIL uses can be moved to the
epilogue (that is, after the second `%%') in the Bison input file. In
this release (2.4.2), Bison already generates its own code to suppress
C preprocessor warnings for YYFAIL, so projects can remove their own
phony uses of YYFAIL if compatibility with Bison releases prior to
2.4.2 is not necessary.
** Internationalization.
Fix a regression introduced in Bison 2.4: Under some circumstances,
message translations were not installed although supported by the
host system.
This is a monthly bugfix release with numerous minor fixes including:
* clone: fix URL too long problem with many heads
* commands: revised documentation of 'default' and 'default-push'
* convert/cvs: skip bad tags
* convert/git: check status when reading output stream
* convert/subversion: fix default URL checker prototype
* copies: properly visit file context ancestors on working file contexts
* diffstat: use ui.plain() instead of ui.interactive()
* dirstate: fix in memory dirstate entries for 1-second race
* dispatch: don't mangle ImportError abort messages
* filemerge: use working dir parent as ancestor for backward wdir merge
* hgrc.5: describe form of config values and mention lists as well
* hgweb: fix attribute error in error response (issue2060)
* log: document the new xml style
* merge: correctly compute the flag for noexec filesystems
* mq: rewrite strip docstrings
* mq: use util.unlink instead of os.unlink and os.removedirs
* patch: don't look for headers in diff lines
* push: fix bug in warning message selection
* revlog: fix lazyparser.iter() to return all revisions (issue2137)
* schemes: fix // breakage with Python 2.6.5 (issue2111)
* static-http: allow clone -r (issue2164)
* subrepo: fix repo root path handling in svn subrepo
* subrepo: propagate and catch push failures
* templates: document missing template variables
* util: fix default termwidth() under Windows
* util: use an explicit prefix for checkexec/checklink temporary files
The Easy Publish and Consume library provides an easy method to:
* publish data per HTTPS
* announce that information via DNS-SD
* find that information
* and finally consume it
You can use this library as key/value store published to the network,
using encryption, authentication and service discovery.
