Next | Query returned 24 messages, browsing 21 to 30 | previous

History of commit frequency

CVS Commit History:


   2011-08-07 10:11:02 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
Changes 0.004:
* bugfix: require bugfixed version of Lexical::SealRequireHints
* document that Perls prior to 5.9.3 don't propagate the right lexical
  state into string eval
* test that handlers are scoped correctly across swash loading
   2010-08-21 18:37:14 by Stoned Elipot | Files touched by this commit (1724) | Package updated
Log message:
Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.

sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
   2010-04-24 18:33:57 by Stoned Elipot | Files touched by this commit (2)
Log message:
Update p5-Attribute-Lexical from version 0.001 to version 0.002.

Pkgsrc changes:
- Adjust dependencies

Upstream changes:
version 0.002; 2010-04-11

  * bugfix: require bugfixed version of Lexical::SealRequireHints (for
    passing package through to required code in pure-Perl version of
    Lexical::SealRequireHints)

  * make all numeric comparisons against $] stringify it first, to avoid
    architecture-dependent problems with floating point rounding giving
    it an unexpected numeric value

  * change Attribute::Lexical::UNIVERSAL POD filename from a .pm to the
    .pod that it should have been

  * in Build.PL, explicitly declare configure-time requirements

  * add MYMETA.yml to .cvsignore
   2010-04-09 10:17:41 by Jens Rehsack | Files touched by this commit (3) | Imported package
Log message:
Importing devel/p5-Attribute-Lexical 0.001

This module manages attributes that can be attached to subroutine and
variable declarations. Although it can be used directly, it is mainly
intended to be infrastructure for modules that supply particular attribute
semantics.

Meanings are assigned to attributes by code which is usually supplied by
modules and which runs at compile time. The built-in mechanism for attribute
control is awkward to use, difficult in particular to enable multiple
attributes supplied by different modules, and it scopes attribute meanings
according to the package of the object to which attributes are being
applied. This module is intended to overcome these limitations.

This module supplies a simple pragma to declare an attribute, associating
the attribute's name with a handler function that implements its semantics.
The declaration is lexically scoped, lasting only until the end of the
enclosing block. A declaration can be overridden, giving an attribute name
a different meaning or making it meaningless, in an inner nested block.


Next | Query returned 24 messages, browsing 21 to 30 | previous