Renaming of files is supported with the previousPath attribute. This also includes the renaming of folders, as the files in the folders also change their name. This all works within the scope of one history.
Problem: In nested history, the specification does not provide mechanisms to rename the folder name of an entire sub-history. In such a case the hashlistreference mechanism of the outer history breaks, because the path to the manifest of the nested history does not exist any more.
Proposed solution: It seems as if the hashlistreference also needs something like a previousPath attribute to indicate that the sub-history and its manifests can now be found at a new place.
Renaming of files is supported with the
previousPathattribute. This also includes the renaming of folders, as the files in the folders also change their name. This all works within the scope of one history.Problem: In nested history, the specification does not provide mechanisms to rename the folder name of an entire sub-history. In such a case the
hashlistreferencemechanism of the outer history breaks, because the path to the manifest of the nested history does not exist any more.Proposed solution: It seems as if the hashlistreference also needs something like a
previousPathattribute to indicate that the sub-history and its manifests can now be found at a new place.