---
- branch: MAIN
  date: Mon Jun 23 03:59:19 UTC 2008
  files:
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-Test-use-ok/Makefile
    pathrev: pkgsrc/devel/p5-Test-use-ok/Makefile@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-Test-use-ok/DESCR
    pathrev: pkgsrc/devel/p5-Test-use-ok/DESCR@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/devel/p5-Test-use-ok/distinfo
    pathrev: pkgsrc/devel/p5-Test-use-ok/distinfo@1.1.1.1
    type: imported
  id: 20080623T035919Z.863a86cd01edf7a24a90cbe27769c81c39e48644
  log: "Import p5-Test-use-ok-0.02\n\nAccording to the Test::More documentation, it
    is recommended to run\nuse_ok() inside a BEGIN block, so functions are exported
    at\ncompile-time and prototypes are properly honored.\n\nThat is, instead of writing
    this:\n\n    use_ok( 'Some::Module' );\n    use_ok( 'Other::Module' );\n\nOne
    should write this:\n\n    BEGIN { use_ok( 'Some::Module' ); }\n    BEGIN { use_ok(
    'Other::Module' ); }\n\nHowever, people often either forget to add BEGIN, or mistakenly
    group\nuse_ok with other tests in a single BEGIN block, which can create subtle\ndifferences
    in execution order.\n\nWith this module, simply change all use_ok in test scripts
    to use ok,\nand they will be executed at BEGIN time.  The explicit space after
    use\nmakes it clear that this is a single compile-time action.\n\nStatus:\n\nVendor
    Tag:\tTNF\nRelease Tags:\tpkgsrc-base\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/p5-Test-use-ok'
  unixtime: '1214193559'
  user: abs