[kepler-dev] [Bug 4578] tracking bug for changes to .kepler

[bugzilla-daemon at ecoinformatics.org]

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

--- Comment #1 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2009-12-02 17:37:03 PST ---
.kepler now has cache and persistent areas like:

.kepler/cache/gamma.msi.ucsb.edu.OpenAuth.1278/modules/actors (etc)
.kepler/persistent/gamma.msi.ucsb.edu.OpenAuth.1278/modules/actors (etc)
.kepler/persistent/gamma.msi.ucsb.edu.OpenAuth.1278/modules/actors/configuration/

The idea is that if a developer writes something into a persistent folder (like
the configuration folder shown above) they're assuming the responsiblity of
dealing with that data during version upgrades. Otherwise they should probably
write their temporary items into the appropriate module's cache dir.

Today in a meeting we decided it would probably be better to move persistent
out of .kepler, and put it somewhere more apparent to the user. For example if
a user's migrating to a different machine, it will be more apparent they should
take their ~/myKepler dir with. By default this might be ~/myKepler/persistent.
We also decided it would be good to put the local repository library folders
(e.g. Actors, Directors, R) into ~/myKepler too. (And "myKepler" was just a
suggestion).

I'm planning to try to move separate the provenance DB back out into it's own
DB inside the provenance persistent folder, and move the kepler DB into the
appropriate cache module folder.

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