Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
0.011 2014-01-06
- add forgotton 0.010 Changelog
0.010 2014-01-06
- bump copyright year
- improve acknowledgements
- rely on BAIL_OUT of Test::More instead of simulating it
0.009 2013-10-25
- add API to allow plugins to improve registration (speeds
up loading)
- switch to ExtUtils::MakeMaker, 'cause Module::Build had
trouble with recent meta spec ...
from 0.007 to 0.008.
pkgsrc changes:
- adjust some URI's for download and homepage
- generated by Packager::Utils
Upstream changes:
0.008 2013-10-19
- introduce pluggable dir sources
- add developer requires for runs from repository clones
0.007 2013-09-21
- Update copyright year (just to make sure everybody recognizes)
0.006 2013-09-20
- Reformatted as per CPAN::Changes::Spec by Neil Bowers
- Fix rt#88616 (test didn't work according to XDG Base Directory
Specification) - thanks to Alex Hartmaier.
- Fix typo in regex for testing the amount of expected directories
- Improve documentation
0.005 2013-09-03
- move to GitHub
- fix xdg_config_dir/xdg_config_home
- commit fox for rt#69263 (includes fix for rt#82696)
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.
This module is a helper for installing, reading and finding configuration
file locations. It's intended to work in every supported Perl5 environment
and will always try to Do The Right Thing(tm).
File::ConfigDir is a module to help out when perl modules (especially
applications) need to read and store configuration files from more than one
location. Writing user configuration is easy thanks to File::HomeDir, but
what when the system administrator needs to place some global configuration
or there will be system related configuration (in /etc on UNIX(tm) or
$ENV{windir} on Windows(tm)) and some network configuration in nfs mapped
/etc/p5-app or $ENV{ALLUSERSPROFILE} . "\\Application Data\\p5-app",
respectively.
File::ConfigDir has no "do what I mean" mode - it's entirely up to the user
to pick the right directory for each particular application.