Displaying 2 results from an estimated 2 matches for "confdoc".
Did you mean:
compdoc
2011 Feb 11
1
[PATCH v2v] Add support for performing automated builds
...syntaxcheck_exclude => [ "COPYING", "COPYING.LIB", "README-NLS" ]
+ syntaxcheck_exclude => [ "COPYING", "COPYING.LIB", "README-NLS" ],
+ PL_files => [ 'virt-v2v.spec.PL' ],
);
$build->add_build_element('confdoc');
diff --git a/MANIFEST b/MANIFEST
index 1ff7e9b..9c2a5df 100644
--- a/MANIFEST
+++ b/MANIFEST
@@ -1,4 +1,5 @@
augeas/README.txt
+autobuild.sh
Build.PL
ChangeLog
COPYING
@@ -47,5 +48,7 @@ v2v/run-v2v-locally
v2v/virt-v2v.conf
v2v/virt-v2v.conf.pod
v2v/virt-v2v.pl
+virt-v2v.spec
+virt-v2...
2010 Feb 12
11
[PATCH 1/9] Convert config file to XML, and translate networks/bridge for all connections
Previously, only the LibVirtXML connection translated network and bridge names
in imported metadata. This change moves this functionality in Converter, making
it available to LibVirt connections as well.
At the same time, the format of the config file is switched to XML. The primary
driver for this is that the allowable syntax of a foreign network/bridge name is
not known. Rather than create a