[dev] [commits] Horde-Hatchery branch master updated. d3fcd5cdd11ada51d44c03fccd529ba9beed543d

[Jan Schneider]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> Let's simply keep the VCS structure completely out of the  
>> discussion. I think everyone is fine about how we organize it out,  
>> and it only complicates the discussion.
>
> Okay. This works for me.
>
>> Let's only talk about how we expect Horde to be installed in the  
>> future. And it shouldn't matter whether it's being installed  
>> through individual tarballs, PEAR, or groupware bundles.
>> The longer we talk about it and the more complications arise and  
>> the more loops we seem to have to jump through to make horde/ work  
>> *next* to the application directories, the less I think it's worth  
>> it.
>>
>> Recapping the pros and cons of both solutions, this is what I think  
>> about them:
>>
>> Live in separate dirs
>> ---------------------
>> + The way our repo is stored => doesn't matter
>> + Maximum flexibility for admins => that they never will use
>> - Extra config needed to determine paths (can this be automated by  
>> installer?) => not true
>> + Simplify some maintenance/building scripts => that already work  
>> fine with the current structure
>> + Better compatibility with distribution packages => distributions  
>> will always do their own stuff anyway, no matter what we do
>>
>> So, if we were about to vote, I'd say: let's leave it like it is  
>> today, it worked in the past and the reasons for changing the  
>> layout are rather weak IMO.
>
> As long as we're willing to evolve as our app structure changes,  
> this is fine with me.

I'm not sure what you mean with this. Of course this structure is not  
set in stone for all eternity. But I'd like to reach a consensus for  
H4 now, so that we can move along.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/