---
- branch: MAIN
  date: Sun Nov 14 20:42:57 UTC 2010
  files:
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-File-ConfigDir/Makefile
    pathrev: pkgsrc/devel/p5-File-ConfigDir/Makefile@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-File-ConfigDir/DESCR
    pathrev: pkgsrc/devel/p5-File-ConfigDir/DESCR@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-File-ConfigDir/distinfo
    pathrev: pkgsrc/devel/p5-File-ConfigDir/distinfo@1.1.1.1
    type: imported
  id: 20101114T204257Z.db65d7109db674f58fbc4cd0095f3a7e3c04edf6
  log: "Importing Perl5 module File::ConfigDir 0.004 into devel/p5-File-ConfigDir.\n\nThis
    module is a helper for installing, reading and finding configuration\nfile locations.
    It's intended to work in every supported Perl5 environment\nand will always try
    to Do The Right Thing(tm).\n\nFile::ConfigDir is a module to help out when perl
    modules (especially\napplications) need to read and store configuration files
    from more than one\nlocation. Writing user configuration is easy thanks to File::HomeDir,
    but\nwhat when the system administrator needs to place some global configuration\nor
    there will be system related configuration (in /etc on UNIX(tm) or\n$ENV{windir}
    on Windows(tm)) and some network configuration in nfs mapped\n/etc/p5-app or $ENV{ALLUSERSPROFILE}
    . \"\\\\Application Data\\\\p5-app\",\nrespectively.\n\nFile::ConfigDir has no
    \"do what I mean\" mode - it's entirely up to the user\nto pick the right directory
    for each particular application.\n\nStatus:\n\nVendor Tag:\tTNF\nRelease Tags:\tpkgsrc-base\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/p5-File-ConfigDir'
  unixtime: '1289767377'
  user: sno