You are not logged in. Log in
|
|
How configuration files are handled during an upgradeFrom $1Table of contentsCombined revision comparison
Briefly: if the file XXX.conf.update.R exists, it is presumed to be an update, and any items in it but not in XXX.conf.R are added to the latter. If an item is in XXX.conf.R but not in XXX.conf.update.R, it is removed, on the assumption that the new version of radR has made the item obsolete. The file XXX.conf.update.R. is renamed so that the update only occurs once. In detail: the following procedure from radRutil.R:rss.do.load.config() is applied to each configurable object XXX: if the file XXX.conf.update.R exists Version from 15:40, 14 Mar 2012
Current versionNote: this page is still valid but less important due to the new recommended upgrade procedure. Briefly: if the file XXX.conf.update.R exists, it is presumed to be an update, and any items in it but not in XXX.conf.R are added to the latter. If an item is in XXX.conf.R but not in XXX.conf.update.R, it is removed, on the assumption that the new version of radR has made the item obsolete. The file XXX.conf.update.R is renamed so that the update only occurs once. In detail: the following procedure from radRutil.R:rss.do.load.config() is applied to each configurable object XXX: if the file XXX.conf.update.R exists |
Powered by MindTouch Core |