virt-manager/MANIFEST.in

# to be included/excluded from the tarball produced by sdist
include COPYING HACKING.md INSTALL.md NEWS README.md
include MANIFEST.in
include setup.py
include virt-*
recursive-include data *
exclude data/gschemas.compiled
recursive-include man *
recursive-include po *
recursive-include tests *
recursive-include ui *
recursive-include virtManager *
recursive-include virtcli *
recursive-include virtconv *
recursive-include virtinst *
global-exclude *.pyc
add MANIFEST.in to specify includes and excludes With no MANIFEST.in, distutils/setup/sdist gets the filelist mostly correct except that it adds in whatever is in the top directory. Using git-ls-files is not a good solution either because a number of additional files (not git managed) will be needed. The solution is to use a MANIFEST.in. All of the toplevel files which are to be included will need to be specified. Also, each directory will need to be specified and unwanted files (e.g., *.pyc) excluded. Other (non-specified) files and directories will be ignored. . Signed-off-by: Gene Czarcinski <gene@czarc.net> 2013-04-09 23:18:59 +04:00			`# to be included/excluded from the tarball produced by sdist`
HACKING: convert to Markdown format. 2016-12-26 14:20:36 +03:00			`include COPYING HACKING.md INSTALL.md NEWS README.md`
add MANIFEST.in to specify includes and excludes With no MANIFEST.in, distutils/setup/sdist gets the filelist mostly correct except that it adds in whatever is in the top directory. Using git-ls-files is not a good solution either because a number of additional files (not git managed) will be needed. The solution is to use a MANIFEST.in. All of the toplevel files which are to be included will need to be specified. Also, each directory will need to be specified and unwanted files (e.g., *.pyc) excluded. Other (non-specified) files and directories will be ignored. . Signed-off-by: Gene Czarcinski <gene@czarc.net> 2013-04-09 23:18:59 +04:00			`include MANIFEST.in`
			`include setup.py`
			`include virt-*`
			`recursive-include data *`
setup: Make gsettings always work regardless of install dir (bz #1267377) Most of this is lifted from 'meld'. The bits are - compile gsettings schemas at setup.py install time - add options to disable that, and use them in the RPM - always pass GSETTINGS_SCHEMA_DIR so gsettings loading always works regardless of the install dir https://bugzilla.redhat.com/show_bug.cgi?id=1267377 2015-11-03 00:19:31 +03:00			`exclude data/gschemas.compiled`
add MANIFEST.in to specify includes and excludes With no MANIFEST.in, distutils/setup/sdist gets the filelist mostly correct except that it adds in whatever is in the top directory. Using git-ls-files is not a good solution either because a number of additional files (not git managed) will be needed. The solution is to use a MANIFEST.in. All of the toplevel files which are to be included will need to be specified. Also, each directory will need to be specified and unwanted files (e.g., *.pyc) excluded. Other (non-specified) files and directories will be ignored. . Signed-off-by: Gene Czarcinski <gene@czarc.net> 2013-04-09 23:18:59 +04:00			`recursive-include man *`
			`recursive-include po *`
			`recursive-include tests *`
			`recursive-include ui *`
			`recursive-include virtManager *`
			`recursive-include virtcli *`
			`recursive-include virtconv *`
			`recursive-include virtinst *`
Simplify MANIFEST Seems to give us the same results 2013-04-13 22:02:29 +04:00			`global-exclude *.pyc`