On Jun 5, 2007, at 8:15 PM, Heikki Toivonen wrote:
Mike Taylor wrote:Currently the Upgrade Notification dialog will be triggered if the following condition is met:Does a repository from a previous Chandler version exist and we arecreating a new repositoryI don't think this describes it exactly enough for discussion. How do wedetermine if a previous version exists? What exactly do you mean by creating a new repository?
A previous version in this context means the presence of a profile directory from a version that isn't the current versions. For example, let's say we are running 0.7.dev for the first time but have run 0.7alpha4 previously. The profile directory would look like this:
.../Open Source Applications Foundation/Chandler/0.7alpha4/fdAB5dw.default/
../Open Source Applications Foundation/Chandler/0.7/fdFW3oi.default/
The upgrade test would see the 0.7alpha4/* directory and see that a
repository directory is found - this would be flagged as a previous
active version.
Creating a new repository is determined by looking in the existing repository directory and detecting that a repository does not exist *but* that the repository create flag is active. This should only happen during the first run.
--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
