---
- branch: MAIN
  date: Sun Jan 27 20:42:17 UTC 2013
  files:
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/p5-FindBin-libs/DESCR
    pathrev: pkgsrc/devel/p5-FindBin-libs/DESCR@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/p5-FindBin-libs/Makefile
    pathrev: pkgsrc/devel/p5-FindBin-libs/Makefile@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/p5-FindBin-libs/distinfo
    pathrev: pkgsrc/devel/p5-FindBin-libs/distinfo@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/p5-FindBin-libs/patches/patch-META.yml
    pathrev: pkgsrc/devel/p5-FindBin-libs/patches/patch-META.yml@1.1
    type: added
  id: 20130127T204217Z.91e8b42ed5383b2dbf380675368b2e3c216309b6
  log: |
    Add p5-FindBin-libs:

    An all-too-common occurrance managing perly projects is being unable
    to install new modules becuse "it might break things", and being
    unable to test them because you can't install them. The usual outcome
    of this is a collection of hard-coded

        use lib qw( /usr/local/projectX ... )

    code at the top of each #! file that has to be updated by hand for
    each new project.

    To get away from this you'll often see relative paths for the lib's,
    which require running the code from one specific place. All this
    does is push the hard-coding into cron, shell wrappers, and begin
    blocks.

    With FindBin::libs you need suffer no more.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/p5-FindBin-libs'
  unixtime: '1359319337'
  user: schmonz