Item12085: Extension installer does not handle shipped rcs ,v files correctly
Priority: Normal
Current State: No Action Required
Released In: n/a
Target Release: n/a
Applies To: Engine
Component: Configure
Branches:
During installation there are a couple of issues:
- The comma is the manifest delimiter. This is being addressed by Item8898 for new packages, but needs to be handled for older packages.
- The related
.txt
file is "checked in" because the previous ",v" file exists on disk, then the ",v" file is overlaid by the shipped file
- The file timestamp on the checked in file is newer than the shipped ",v" file, resulting in an extra revision when the topic is viewed.
The installer assumes that if
,v
rcs files exist on disk, then there have been local modifications that should be retained in history and forces a "check-in" even for files marked
(noci)
in the manifest. When a
,v
file is shipped, we will end up discarding history of local modifications. However this is all done for just a single instance. The
CompareRevisionsAddOn ships a demo file with history to show capabilities of the topic revision history.
When a
,v
file is shipped, we need to flag the related file to ensure that it is copied rather than checked in, so that revision history is correct. Local modifications will be lost from history, but would still be in the backup archive taken during extension installation.
--
GeorgeClark - 22 Sep 2012
Another very long standing issue. Deferring to 1.2.
--
GeorgeClark - 02 Nov 2012
Changing this to no action. We should not ship ,v files under any conditions, especially now that we have the PlainFile store.
--
GeorgeClark - 02 Dec 2014