squishing install and deploy dirs together

[Jim R. <jm...@qu...>]

Hi,

I'm considering a model where the install, deploy and reveal dirs are 
all in AFS.  As I understand it, most of the arguments for having 
distinct install and deploy dirs disappear in this context.  (I can't 
think of any good reasons to have separate dirs, except that you have to 
avoid trampling on existing deployed code that is being used.)  Thus, 
I'm thinking that the ideal configuration is one where you install into 
the deploy dir and just leave it there -- instead of copying it back to 
install, etc.

I haven't gotten as far as looking into exactly how one might achieve 
this.  Before I do, I have have some questions:

1.) In this context, are there reasons to keep install and deploy 
distinct?  If so, what?

2.) Do you have guidance for me in terms of the general approach to 
making them be the same?  (i.e, Where do I hack?)  Is this going to be a 
big job or a small one?  Has anyone done something similar that would be 
useful as a starting point?

3.) Am I out of my mind?

Jim