[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 #1 from jianwu <jianwu at sdsc.edu> 2012-07-27 10:10:20 PDT ---
After discussing with Derik, the information about the bug is clearer.

I can reproduce the first scenario for kepler-2.2. The reason is because
Kepler-2.2 reinstall will not overwrite
~/KeplerData/kepler.modules/build-area/modules.txt. So if the modules.txt is
changed by other kepler versions or suites, Kepler 2.2 won't start.

The phenomenon is different for Kepler 2.3. After uninstallation and
re-installation, Kepler 2.3 can start correctly (even
~/KeplerData/kepler.modules/build-area/modules.txt might be set by other
versions). But 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. This means it didn't overwrite modules.txt 

Before we do any changes, I think we can agree on what the correct behavior it
should be. In my opinion, re-installation should replace both existing version
and existing suite, no matter this re-installation is newer or older than other
Kepler versions on the machine.

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