[kepler-dev] proposed changes to .kepler

[Derik Barseghian]

Kepler devs,

After some discussion with Aaron, Ben, Dan, and Chad, I'm wondering if  
anyone objects to dividing .kepler into two different areas -- there  
would be areas for 1) persistent items (e.g. provenance database) and  
2) temporary items (e.g. cache). This would make it more apparent  
which things could be deleted without serious ramification (temp/),  
and the idea would be items in peristent/ should stick around and be  
dealt with during kepler upgrades for backwards compatibility.

Also, I think we should utilize the InstanceAuthNamespace in these  
paths, so that items from different Kepler instances are separated.

This could look like (imagine multiple namespace dirs):

a)
.kepler/perisistent/gamma.msi.ucsb.edu.OpenAuth.1278/
.kepler/temp/gamma.msi.ucsb.edu.OpenAuth.1278/

or b)
.kepler/gamma.msi.ucsb.edu.OpenAuth.1278/persistent/
.kepler/gamma.msi.ucsb.edu.OpenAuth.1278/temp/

or c)
.kepler_temp/gamma.msi.ucsb.edu.OpenAuth.1278/
.kepler_persistent/gamma.msi.ucsb.edu.OpenAuth.1278/

I prefer a).

This partly came out of a discussion of bug 4514. I think the  
configuration files could be stored beneath these new paths, probably  
in persistent.
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4514

A better solution might be to just have a .kepler to store temporary  
things, and to store persistent items in an OS-appropriate location,  
but I think this might be a larger change than we want to take on at  
the moment, as we try to get 2.0 out of the door.

Let me know what you think,
Derik