---
- branch: MAIN
  date: Tue Oct 11 12:24:33 UTC 2016
  files:
  - new: '1.2325'
    old: '1.2324'
    path: pkgsrc/devel/Makefile
    pathrev: pkgsrc/devel/Makefile@1.2325
    type: modified
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/py-vcversioner/DESCR
    pathrev: pkgsrc/devel/py-vcversioner/DESCR@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/py-vcversioner/Makefile
    pathrev: pkgsrc/devel/py-vcversioner/Makefile@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/py-vcversioner/PLIST
    pathrev: pkgsrc/devel/py-vcversioner/PLIST@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/py-vcversioner/distinfo
    pathrev: pkgsrc/devel/py-vcversioner/distinfo@1.1
    type: added
  id: 20161011T122433Z.defa097e995e6c04fcd1c1cfda258f57b48b391c
  log: |
    New package, py-vcversioner, from pkgsrc-wip.

    You can write a setup.py with no version information specified, and vcversioner
    will find a recent, properly-formatted VCS tag and extract a version from it.

    It's much more convenient to be able to use your version control system's
    tagging mechanism to derive a version number than to have to duplicate that
    information all over the place. I eventually ended up copy-pasting the same
    code into a couple different setup.py files just to avoid duplicating version
    information. But, copy-pasting is dumb and unit testing setup.py files is hard.
    This code got factored out into vcversioner.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel'
  unixtime: '1476188673'
  user: bsiegert