a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
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!
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=...").
#========================================================================
# Version 1.66 Date: 2007/07/06 (Andy Wardley)
#========================================================================
* Removed File::HomeDir from the test scripts.
#========================================================================
# Version 1.64 Date: 2007/01/02 (Adam Kennedy)
#========================================================================
* Bug fix to prevent crashing for users with no home directory
* Increase File::HomeDir dep to 0.61 which supports no home directory
cases properly.
#========================================================================
# Version 1.63 Date: 2006/08/03 (Adam Kennedy)
#========================================================================
* Unified version numbers and removed repository magic
* Removed "use warnings" to get the Perl version dependency back to 5.005
* Removed "use base Exporter" which doesn't always work
* Use File::HomeDir to find $HOME instead of doing it ourself, sorta
* Fixed a POD bug in AppConfig::Sys and added a 99_pod.t test
* Added a LICENSE file
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.
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
* Add "heredoc" style quoting.
* Added POSIX style '=value' suffixes to --parameters. Thus '--foo=bar'
is now equivalent to '-foo bar'.
* Added AppConfig::CGI module to parse CGI script parameters.
* Added cgi() delegate method to AppConfig to instantiate and call
AppConfig::CGI.
* Provide default options for LIST and HASH data types.
* Allow '$' to be escaped (e.g. \$) to suppress variable expansion in files.
* Applied patch from John Salmon to allow comments to appear anywhere
on a line, not just at the beginning.
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
AppConfig is a bundle of perl5 modules for parsing configuration files
and command line arguments. It has a very powerful configuration file
processor and a simple, efficient mechanism for parsing command line
arguments. It also will use the Getopt::Long module where available
to extend its own command line parsing abilities.
Provided by Nathan Ahlstrom <nrahlstr@winternet.com> in PR #12637.
