[dev] [commits] Horde branch sesha updated. 026f263152c0c92706e44df5a895c94392bea32d

[Michael J Rubinsky]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Vilius ?umskas <vilius at lnk.lt>:
>
>> Hello,
>>
>> Saturday, January 14, 2012, 6:02:47 PM, you wrote:
>>
>>> Quoting Ralf Lang <lang at b1-systems.de>:
>>
>>>> The branch "sesha" has been updated.
>>>> The following is a summary of the commits.
>>>>
>>>> from: b50c5dfeb6d97183c4afd0d2ade3a229146836b2
>>>>
>>>> 36727fb Set license to GPL-2.0, current text version
>>>> 7c07085 required dependencies
>>>> 026f263 [rla] Converted to Horde 4 Framework
>>
>>>> commit 7c07085f9fcca64faf059b17fb393d542cf88a39
>>>> Author: Ralf Lang <lang at b1-systems.de>
>>>> Date:   Sat Jan 14 15:40:35 2012 +0000
>>>>
>>>>    required dependencies
>>>>
>>>> sesha/package.xml |   42 ++++++++++++++++++++++++++++++++++++++++++
>>>> 1 files changed, 42 insertions(+), 0 deletions(-)
>>>>
>>>> http://git.horde.org/horde-git/-/commit/7c07085f9fcca64faf059b17fb393d542cf88a39
>>
>>
>>> Don't forget things that might not be obvious to the CompatInfo
>>> script; Horde_Auth, Horde_Autoloader, Horde_Core, Horde_Util,
>>> Horde_Notification, Horde_Log, Horde_Perms etc...
>>
>> Is this really needed in every application? Wouldn't this be picked up
>> by  the  "horde" dependency? I'm asking because I would need to adjust
>> ulaform/package.xml then.
>
> Techically this would be more correct, but since this would generate  
> huge lists of dependencies, our current (unwritten) policy is to  
> only list dependencies that are not pulled in by either horde or  
> Horde_Core anyway.

When was this decided? I thought it was the opposite. If I look at our  
other apps like e.g., IMP or Kronolith. I see all the dependencies  
that are also required by Core and Horde.  I don't have a strong  
opinion one way or the other, though I would lean towards being more  
complete. Just want to know so that we can be consistent.


-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org