[kepler-dev] [Bug 5398] Re-install of Kepler-x.y doesn't overwrite modules.txt

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5398

--- Comment #2 from jianwu <jianwu at sdsc.edu> 2012-07-30 14:17:55 PDT ---
After discussion with Dan, we think it is correct to keep its suite
configuration even a Kepler version is uninstalled and re-installed. Many
software uninstallation and re-installation keep user settings.

It means the following behavior is correct: if a user install kepler-2.3.0,
download and switch to reporting-2.3.0, uninstall and reinstall kepler-2.3, and
it start into reporting-2.3.

~/KeplerData/kepler.modules/build-area/install-id.txt records the Kepler
version number. Since kepler 2.3, if the install-id.txt in ~/KeplerData/ and
the install-id.txt in installation path do not match (no matter which is
newer), Kepler will first copy modules.txt and install-id.txt from installation
path to ~/KeplerData/kepler.modules/build-area/ and overwrite the old texts in
the directory. It means Kepler can always start correctly after Kepler 2.3.

So this bug is only in Kepler 2.2, not in later Kepler versions. 

We can discuss it during the next 2.4 release call. My current opinion is that
we need to do nothing about this bug for 2.4 release.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.