OK, on second thought, I think I'm going to revert this change.
If you're a developer building Wireshark, then you probably want the latest help available, not a snapshot from some time in the past. The latest is either the one you built yourself if you've got the HTML Help Worshop tools or the online help, not the one extracted from the user-guide.zip file.
But then why do we download the user-guide.zip as part of the setup to begin with?
- Chris
________________________________________
From: wireshark-commits-bounces@xxxxxxxxxxxxx [wireshark-commits-bounces@xxxxxxxxxxxxx] On Behalf Of cmaynard@xxxxxxxxxxxxx [cmaynard@xxxxxxxxxxxxx]
Sent: Monday, September 24, 2012 9:03 PM
To: wireshark-commits@xxxxxxxxxxxxx
Subject: [Wireshark-commits] rev 45116: /trunk/ /trunk/: Makefile.nmake config.nmake
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=45116
User: cmaynard
Date: 2012/09/24 06:03 PM
Log:
We're downloading the user-guide as part of the setup, so we might as well copy it to the install directory. If someone has built a more up-to-date version of the user-guide in the docbook directory, then it will just overwrite this one, but for most developers, I don't think they're building their own, so at least this way they'll still have a local copy of the user-guide. If optional is the preferred default, then we can change config.nmake and just comment out UG_DIR and mark as "optional" instead of "recommended".
Directory: /trunk/
Changes Path Action
+1 -0 Makefile.nmake Modified
+5 -0 config.nmake Modified
--
CONFIDENTIALITY NOTICE: The information contained in this email message is intended only for use of the intended recipient. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately delete it from your system and notify the sender by replying to this email. Thank you.