tigran
06-03-2009, 03:40 PM
I have my patch configured in a very specific way to provide "FULL PATCHING" without the need to manually add new versions through new tabs.
In one tab, named 0.0.0.0, I only include the latest version of keyfile. On the other tab, I have a dynamic path through ## constant that contains the latest version of key file and a bunch of folder references for the rest of the application files.
In older version of patch, such as 3.0.2.0, compiling the patch would include absolutely all files because a key file was marked as "forced to install" and the folder references in the newer version tab were included completely because tab 0.0.0.0 did not have them listed at all.
In the newer versions however (3.0.3.0 and 3.5), compiler behaves totally different - folder references listed in the newer version tab but NOT listed in the 0.0.0.0 tab are skipped!
Why such a change in the behavior? Can you suggest a solution? Thanks!
In one tab, named 0.0.0.0, I only include the latest version of keyfile. On the other tab, I have a dynamic path through ## constant that contains the latest version of key file and a bunch of folder references for the rest of the application files.
In older version of patch, such as 3.0.2.0, compiling the patch would include absolutely all files because a key file was marked as "forced to install" and the folder references in the newer version tab were included completely because tab 0.0.0.0 did not have them listed at all.
In the newer versions however (3.0.3.0 and 3.5), compiler behaves totally different - folder references listed in the newer version tab but NOT listed in the 0.0.0.0 tab are skipped!
Why such a change in the behavior? Can you suggest a solution? Thanks!