pkgsrc/devel/py-vcversioner/PLIST

@comment $NetBSD: PLIST,v 1.1 2016/10/11 12:24:33 bsiegert Exp $
${PYSITELIB}/${EGG_INFODIR}/PKG-INFO
${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt
${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt
${PYSITELIB}/${EGG_INFODIR}/entry_points.txt
${PYSITELIB}/${EGG_INFODIR}/top_level.txt
${PYSITELIB}/vcversioner.py
${PYSITELIB}/vcversioner.pyc
${PYSITELIB}/vcversioner.pyo
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. 2016-10-11 14:24:32 +02:00			`@comment $NetBSD: PLIST,v 1.1 2016/10/11 12:24:33 bsiegert Exp $`
			`${PYSITELIB}/${EGG_INFODIR}/PKG-INFO`
			`${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt`
			`${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt`
			`${PYSITELIB}/${EGG_INFODIR}/entry_points.txt`
			`${PYSITELIB}/${EGG_INFODIR}/top_level.txt`
			`${PYSITELIB}/vcversioner.py`
			`${PYSITELIB}/vcversioner.pyc`
			`${PYSITELIB}/vcversioner.pyo`