On 08/22/08 11:40, Jan Holesovsky wrote:
Hi Ingo,
On Friday 22 of August 2008, Ingo Schmidt-Rosbiegal wrote:
Please, cannot this just be automatically generated before the release,
and be done with that? Depending on the people that they don't forget to
add some PATCH thing somewhere is so error-prone :-(
I fully agree with you, that this is very error-prone and should be
automated. Unfortunately an automation process is pretty difficult. It
is not clear, which files have changed because of a bug fix and which
files have only changed because they were built again. If a project XYZ
is built in a m3 and delivers a xyz.dll and without making code changes
you build it in a m4 again, the resulting xyz.dll is different from the
library from m3. At minimum the differences are the build date and the
build id. So a simple check of changed files would include nearly all
files into a patch. So at the moment our build environment does not
allow such an automated process. But if you have a better idea for such
a process, every help is very appreciated.
From what I know, objdump exists for Windows as well (in Cygwin) - couldn't
that be used? I can imagine doing objdump -d on the old and the new version,
some sed-action to filter out the unimportant changes, and diff - but
unfortunately I don't know how the Windows output of the tool looks like :-(
Don't know if objdump -d could really be used to compute a decent set
of PATCH flags, for libraries and executables. What about files other
than libraries and executables? Would the simply heuristic "diff says
files differ implies PATCH flag" really work, or would it come up with
an unacceptably large number of false positives?
(Re Windows: If we decide to use Microsoft Installer MSP patches for
OOo 3, then for Windows manually set PATCH flags would indeed be
unnecessary, as an MSP is computed as the diff of two installation sets.
The neat part is that only the different parts of a file are included
in an MSP, not the whole file, so that even if there are many false
positives---like build time stamps, or mangled names for anonymous C++
namespaces---the resulting MSP will not get excessively large.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
