On 19.02.2010 03:25, INADA Naoki wrote: > Very thanks for advice. You're welcome.
>> Use only the first three levels in version info >> (A,B,C in A.B.C.X where A,B,C in 0..65535) and put the >> version info into all exe and dll files as well (X is >> ignored by Windows installer when deciding to exchange things). >> Count up at least C for every new msi you release. > > Should I change version info in all dll including Python25.dll, zlib.dll, etc? > Not only shell extension dll? > No. I was talking about adding version resource info to all dll/exe's that are built. Not changing externally delivered items like python26.dll that already have one. For example the python26.dll I have here, already *does* have a file version 2.6.4150.1013, which looks like the Python guys know what they are doing. That is, if they publish a new python26.dll, it will most likely have its first three version numbers changed. Which is perfect and sufficient. If you do package that into your installer, modifying that file version would be pointless and dangerous, since it might even break signatures. Don't change the version resource info of externally delivered items. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
