I am close to releasing WP-MIRROR 0.6. It will exhibit reliability
and performance improvements in all areas of operation.
As a part of the development process, I have been testing `mwxml2sql'
with a view towards using it to replace `importDump.php' in WP-MIRROR
0.6. These tests have worked out well.
There are however some issues that I should discuss with you.
I distribute WP-MIRROR as a DEB package. In order to use `mwxml2sql',
I would have to package your tools as a separate DEB package. This I
have done. However, in the process, I had to apply some patches; and
the question now arises as to how to submit them upstream.
I have patched the `Makefile' that you distribute with `mwxml2sql'
because: a) the `install' target must use `install' rather than `mv';
and b) it lacked a `deinstall' target. Both changes are required by
3) Man pages
Man pages are also required by Debian policy. To that end, I have
written man pages for `mwxml2sql', `sql2txt', and `sqlfilter'.
However, the better approach would be to patch those tools so that man
pages could automatically be generated using `help2man'. The later
approach has the benefit of eliminating duplication, and hence, helps
keep code and documentation in sync.
I would like to know:
a) if patches are welcome upstream; and, if so,
b) what procedures you prefer for submitting, reviewing, and applying
c) whether you would prefer that I submit the man pages I wrote, or
submit patches to your utilities to make them compatible with
Xmldatadumps-l mailing list
Xmldatadumps-l <at> lists.wikimedia.org