[kepler-dev] [Bug 5457] Mac OS X: Kepler.app should display module error messages in a window

[bugzilla-daemon at ecoinformatics.org]

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

--- Comment #4 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2011-08-23 19:45:08 PDT ---
I believe I've created a solution to this bug locally, but the solution is not
backwards compatible in so far as 2.2's kepler.sh, Kepler.app, and kepler.exe
will fail to start once 2.3 has been installed and started once. We could
recommend people uninstall 2.2 so they're not tempted to try this. Switching
back and forth between 2.2 and 2.3 using 2.3's Module Manager will work. Let me
know if this doesn't sound acceptable to you. Clearly it's not ideal. The bug
here is to do with keeping modules and files used by the build system to start
kepler in two places, the Kepler application folder of course, and
KeplerData/kepler.modules/. The issue is that the files in
KeplerData/kepler.modules are not overwritten during a new install, or when
switching between versions, and so start up can fail when incompatible
KeplerData/kepler.modules/ files exist.

Another solution is to simply not include use.keplerdata in the installers, but
this takes away our ability to let users without write permission to the
application area download and use different modules.

Personally I don't think we should be storing the application in 2 places, it
complicates things and uses extra space. I believe the original intent of using
 KeplerData/kepler.modules for module downloads was to allow users to download
different modules and change suites when they don't have write access to the
application area. However I think we should probably just behave like other
apps. If a user wants to download add-ons, they should have to get admin
access. Or the app should just be entirely in their own space from install. But
this may have to wait for 2.4.

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