People are already using it, so these docs are certainly better than
no docs at all. Markup is mostly missing and the layout is probably
ugly, but this can be fixed later.
Question: there are references to MS docs for the CSIDL_... constants
and the IShellLink interface. Are these pointers sufficient, or should
the MS docs reworded and repeated here?
avaliable in the Python 2.2 branch.
I've left out some flags which are more thought for debugging, if
someone needs them, he can always look at the output of --help.
I'm sure Fred will make some adjustments, so I'll only mark this as a
2.2 bugfix candidate.
There are more options available in the current CVS bdist_wininst,
I will document them after this is in.
there is no need to clutter a reader's life with those useless things.
Make the snippets of Python code conform to the standard style.
Suppress the "Contents" page for HTML; it is not needed for small documents
in the online environment since LaTeX2HTML generates lots of tables of links
anyway.
Various markup consistency nits.
this was posted to distutils-sig in.
Here is what I've hacked together over some spare time
at the weekend. I would appreciate feedback, as I've told
before I'm neither a great author, nor native english speaker,
nor anything else.
Mostly I've completed (and written) docs for bdist_wininst
(where I'm an experert for), also I've started some stuff
for the data_files and scripts option.
Should I continue in this way? Would others like to jump in?
