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!
pkgsrc changes:
- Adding license (perl5 license)
Upstream changes:
1.23 - Fri Jul 17 03:04:38 2009
* Move everything to git and finally make a release
1.22_03 - Tue Jul 29 21:14:49 2008
* Fixed bug for missing file: previously the missing file
name was passed through to run_t_files, although without
the t/ added to its path. Test::Manifest should only
warn about and skip missing files.
1.22_02 - Thu Jan 24 06:13:13 2008
* File path and unlink fixes for VMS (RT #32061). Let's see if this works.
1.22_01 - Sun Jan 6 14:18:46 2008
* Changed test file names to only have one dot in them so they
work on VMS and ODS-2 file systems: RT #32061
* This is a test release.
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
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=...").
1.17 - Thu Feb 22 13:20:23 2007
* Updated to Sourceforge's SVN repository
* Dist conforms to META 1.2 spec
* No feature changes, so no big hurry to upgrade
1.16 - Tue Aug 29 17:43:16 2006
* Added an experimental feature to grab file names from additional
files. Just specify which other files to grab file names from:
;include names_in_this_file.txt
See the docs for get_t_files().
* This is an experimental feature. This feature is experimental.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
