summaryrefslogtreecommitdiff
path: root/MANIFEST.in
Commit message (Collapse)AuthorAgeFilesLines
* Add DESIGN.mdCole Robinson2020-01-261-1/+1
| | | | | | | This is derived from the mailing list discussion here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00108.html Signed-off-by: Cole Robinson <crobinso@redhat.com>
* Remove virt-convertCole Robinson2020-01-241-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | This was raised here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html Quoting from that: """ virt-convert takes an ovf/ova or vmx file and spits out libvirt XML. It started as a code drop a long time ago that could translate back and forth between vmx, ovf, and virt-image, a long dead appliance format. In 2014 I converted it to do vmx -> libvirt and ovf -> libvirt which was a CLI breaking change, but I never heard a peep of a complaint. It doesn't seem to do a particularly thorough job at its intended goal, I've seen 2-3 bug reports in the past 5 years and generally it doesn't seem to have any users. Let's kill it. If anyone has the desire to keep it alive it could live as a separate project that's a wrapper around virt-install but there's no compelling reason to keep it in virt-manager.git IMO """ Nothing has changed since then, so here is the removal. Signed-off-by: Cole Robinson <crobinso@redhat.com>
* Move virtcli/cliconfig.py to virtinst/buildconfig.pyCole Robinson2019-06-141-1/+0
| | | | | There's really no reason for the split, just contain it all within virtinst for simplicity
* docs: Multiple updatesCole Robinson2019-05-161-1/+1
| | | | | | | | * Renaming HACKING.md to CONTRIBUTING.md, special github naming * Point to modern virt-manager.org bug link * Mention option to use github issue tracker * Point to the github wiki for more contribution docs * Many minor updates
* tests: test_urls: Look for manual.ini in ~/.config/virt-managerCole Robinson2018-04-031-1/+0
| | | | Rather than deal with ignoring it in the source tree
* tests: test_urls: Simplify adding in local testsCole Robinson2018-01-061-0/+1
| | | | | I'll use this to scoop up local ISOs for comprehensive testing locally.
* NEWS: convert to Markdown format.Mario Trangoni2017-02-161-1/+1
|
* HACKING: convert to Markdown format.Mario Trangoni2017-02-161-1/+1
|
* INSTALL: convert to Markdown format.Mario Trangoni2017-02-161-1/+1
|
* spec: README->README.mdCole Robinson2017-02-051-1/+1
| | | | And fix the MANIFEST as well
* setup: Make gsettings always work regardless of install dir (bz #1267377)Cole Robinson2015-11-021-0/+1
| | | | | | | | | | | 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
* MANIFEST: Drop transifex filesCole Robinson2015-09-231-1/+0
|
* MANIFEST: Remove some missing filesCole Robinson2015-04-061-2/+0
|
* Remove AUTHORSCole Robinson2013-04-211-1/+1
| | | | | | Kind of a maintenance pain, and it's just poorly duplicating info from the git logs. We could autogenerate this but I don't really have the interest in figuring it out. Patches welcome :)
* Remove virt-manager-tuiCole Robinson2013-04-181-1/+0
| | | | | | | | | Was originally added with hopes for being used in an ovirt related product, but was more or less a code dump, and the author has been allocated to other things. He confirmed it's okay to remove. That, and it's currently broken, and we've had approximately 0 user feedback since it was committed.
* Simplify MANIFESTCole Robinson2013-04-131-8/+1
| | | | Seems to give us the same results
* add MANIFEST.in to specify includes and excludesGene Czarcinski2013-04-101-0/+26
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>
View Lorry Controller Status