[4.0] Improve the generator tool for lists of files and folders to be removed or renamed on update #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request for Issue # .
Replaces #20 .
Summary of Changes
This pull request (PR) is just to document the changed script "build/deleted_file_check.php" which I am currently using to generate the lists of deleted files and folders and renamed files for updating script.php.
The changes in the script are:
This allows to execute a sequence of comparisons, see description below on how I use the changed script with a shell script to completely rebuild the lists.
For an example see [4.0] Remove _com_joomlaupdate.scss from deleted files in script.php joomla/joomla-cms#36161 .
The version numbers are read from the manifest XML files "administrator/manifests/files/joomla.xml" of the "from" and "to" directories.
Testing Instructions
Currently I use following Bash script to generate the lists for the 4.0-dev branch:
When keeping the intermediate results from comparing older 4.0 versions since Beta 1, it only needs to do the first comparison from current 3.10-dev to current 4.0-dev and then the last 2 comparisons. The 2nd last because something might have been forgotten in script.php when the last release was made, and the last one for the last release and the current branch.
At the end I can take the complete content of each file, intend it by 3 tabs and copy it into script PHP and can see the changes in Git.
Then it needs only 3 manual steps:
This can be automated later with further improvements, but the question now is if what I am doing here is the right way to go.
For 4.1-dev I run the following shell script after having run the previously mentioned one for 4.0-dev:
Actual result BEFORE applying this Pull Request
I have to identify and remove duplicates myself from the right section of the deleted files and folder lists in script.php.
I have to remove files or folders from the lists which once had been removed and later been added back between releases.
Expected result AFTER applying this Pull Request
Files and folders which have been identified to be removed when updating from the previous major (or minor) release on another branch, e.g. in case of J4 from 3.10, are not to be removed again when updating from a previous version of the current release to be checked.
When some file or folder is removed between 2 versions and later added back with another, later version, the tool is able to handle that yet and remove them from the lists.
Documentation Changes Required
There is no documentation yet on how to use deleted_file_check.php.