Also:
- install gitweb and related stuff (from Simon Kuhnle)
- fix paths in some manpages (noticed by mk@)
- 64bit for date.c fix went upstream
Thanks guys!
jdk/1.7 package to bootstrap
- prevent users from using native_bootstrap or jdk17_bootstrap when
the required package is not pre-installed
"looks good" sthen@
Out of the box Moose only provides very barebones cloning support in
order to maximize flexibility.
This role provides a clone method that makes use of the low level
cloning support already in Moose and adds selective deep cloning based
on introspection on top of that. Attributes with the Clone trait will
handle cloning of data within the object, typically delegating to the
attribute value's own clone method.
Hash::Util::FieldHash using perltie. When Hash::Util::FieldHash is
available it will use that instead.
This way code requiring field hashes can benefit from fast, robust field
hashes on Perl 5.10 and newer, but still run on older perls that don't
ship with that module.
Vstr is a string library designed for network communication. Its
design uses blocks of ptr+length data, so adding, substituting, and
deleting data are all fast operations. It has a full API of all the
usual string tasks: searching, comparing, splitting, substitution,
converting between upper and lower case, and parsing numbers and
strings. Has a full POSIX and ISO 9899:1999 compliant printf()
implementation including gcc warning compatible custom formatters.
The YAML specification is huge. Really, really huge. It contains all
the functionality of XML, except with flexibility and choice, which
makes it easier to read, but with a formal specification that is more
complex than XML.
The original pure-Perl implementation YAML costs just over 4 megabytes
of memory to load. Just like with Windows .ini files (3 meg to load)
and CSS (3.5 meg to load) the situation is just asking for a YAML::Tiny
module, an incomplete but correct and usable subset of the
functionality, in as little code as possible.
This module lets you defer actions that will take place when the control
flow returns into an upper scope. Currently, you can hook an upper
scope end, or localize variables, array/hash values or deletions of
elements in higher contexts. You can also return to an upper level and
know which context was in use then.
DateTime::Set is a module for datetime sets. It can be used to handle
two different types of sets:
* Fixed sets of predefined datetime objects. For example, if we wanted
to create a set of datetimes containing the birthdays of people in
our family.
* Recurring sets, such as "every Wednesday", or "noon on the 15th day
of every month". This type of set can have fixed starting and ending
datetimes, but neither is required.
Set::Infinite is a Set Theory module for infinite sets.
A set is a collection of objects. The objects that belong to a set are
called its members, or "elements". As objects we allow (almost)
anything: reals, integers, and objects (such as dates).
Note that there is no account for
- the order of elements. For example, {1,2} = {2,1}.
- repetition of elements. For example, {1,2,2} = {1,1,1,2} = {1,2}.
dot.conf is a simple-to-use and powerful configuration-file parser
library written in C. The configuration files created for dot.conf look
very similar to those used by the Apache Webserver.
Upstream bug (now fixed) sets MODPY_EGG_VERSION=unknown, so we have to
use that for now. Also, locale stuffs moved to i18n module. No bump
because it didn't package anyway. Sigh.
