From: "Martin v. Löwis"
As for more documentation on the mechanisms of msi.py itself: I have asked a colleague to go through the file and comment on parts of Python code that might be unclear. However, I have the concern that all his questions are likely answered in MSDN - so I'd be really curious what documentation is lacking that is *not* part of MSDN.
I wouldn't worry too much about that. I've never found it easy to follow the documentation on building MSIs (it is a *long* time since I tried, maybe things have improved). A bit of duplication wouldn't harm here. Paul. __________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. __________________________________________________________________________
Moore, Paul wrote:
However, I have the concern that all his
questions are likely answered in MSDN - so I'd be really curious what documentation is lacking that is *not* part of MSDN.
I wouldn't worry too much about that. I've never found it easy to follow the documentation on building MSIs (it is a *long* time since I tried, maybe things have improved). A bit of duplication wouldn't harm here.
My problem is that I have no clue what bits deserve duplication. To fully understand the thing, starting from scratch, you need atleast 50 pages of text. This would exceed the actual lines of code by a great number, and it would be like explaining Python syntax and semantics in comments of a Python script. Regards, Martin
[Martin v. Löwis, on documenting MSI-building]
My problem is that I have no clue what bits deserve duplication. To fully understand the thing, starting from scratch, you need at least 50 pages of text. This would exceed the actual lines of code by a great number, and it would be like explaining Python syntax and semantics in comments of a Python script.
I think you can assume basic familiarity with MSI-building. Then, like anything else, you comment parts you found especially difficult, confusing, subtle, or delicate to work out -- even if they're clearly covered somewhere in the multiple gigabytes of MSDN verbiage, and it was just hard for you to find where. Sometimes crucial details are buried in footnotes. Or, if it's like any other MS API I've ever used, sometimes crucial details are plain missing, and "the thing that worked" was the result of a dozen or ten poke-and-hope attempts.
participants (3)
-
"Martin v. Löwis" -
Moore, Paul -
Tim Peters