http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5505
Matt Jones <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Matt Jones <[email protected]> 2011-10-06 13:00:17 PDT --- Derik and I went back and forth about this last month. For me, one of the compelling reasons to go with a versionless directory is that Kepler now has the feature of switching versions via the ModuleManager on the fly. So, I might install 2.3, but then load a workflow in strict mode that switches the installed version of Kepler to 2.1. It would be weird to have this 2.1 install be pressent in a 2.3 labeled directory. Also, there are efficiencies to be had by installing all of the modules in one location, so they can be found and need not be needlessly re-downloaded when the MM switches from version to version. Finally, I think it is the installer/MM's job to transparently switch from version to version, and that the 'cruft' from previous versions really shouldn't/can't get in the way. If it does, then the MM has a bug, because it is supposed to by design be able to switch from one version to another seamlessly. So I voted for plain "kepler" as the install directory. -- Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ Kepler-dev mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
