[dev] Split Git

Michael M Slusarz slusarz at horde.org
Tue Nov 25 02:26:43 UTC 2014


Quoting Jan Schneider <jan at horde.org>:

> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Michael M Slusarz <slusarz at horde.org>:
>>
>>> Quoting Jan Schneider <jan at horde.org>:
>>>
>>>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>>>
>>>>> Quoting Jan Schneider <jan at horde.org>:
>>>>>
>>>>>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>>>>>
>>>>>>> - Installation of code from git repos can be facilitated by a script.
>>>>>>> - This script can create/clone the git repos as needed.
>>>>>>
>>>>>> And update, and diff, and commit, and probably all the major  
>>>>>> git stuff. Wait, why did I argument against sub-tree again? :)
>>>>>>
>>>>>> Some extra sugar would be if you could checkout one repo, and  
>>>>>> have all dependent packages' repos checked out too.
>>>>>
>>>>> This would be great... although I think this will require  
>>>>> digging into PEAR code in order to grab the required  
>>>>> dependencies (I really don't want to be writing PEAR parsing  
>>>>> code at this stage).
>>>>
>>>> We already have a PEAR parser.
>>>
>>> We have a PEAR parser that programatically will give you the list  
>>> of packages/channels you need to install given a single  
>>> package.xml file?  I've spent hours looking for this, so this is  
>>> fantastic news - where is it located?  (This underscores the need  
>>> for us to keep all install-related code in a single location).
>>
>> It's in the components package. You can get a dependency tree via:
>>
>> horde-components path_to_package deps -deps --allow-remote --alldeps
>>
>> You can also include the --no-tree option to get a YAML format  
>> listing instead of a formatted tree.
>
> And it's built on top of Horde_Pear.

Huh.  I was looking for something like this when I was writing the  
beta of the PHAR installer, since this is exactly what we needed there.

Started to formulate checklist/TODO at:  
http://wiki.horde.org/Project/SplitGitRepo

michael

___________________________________
Michael Slusarz [slusarz at horde.org]



More information about the dev mailing list