[dev] Git splitting

[Michael J Rubinsky]

Quoting Michael M Slusarz <slusarz at horde.org>:

> 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 Michael M Slusarz <slusarz at horde.org>:
>>>>
>>>>> The next step will be to determine how we can use PHP composer  
>>>>> to allow developers to assemble the disparate repos into a  
>>>>> format that we can actually use on a day-to-day basis.  Should  
>>>>> not be that difficult - we should only need to replace/alter the  
>>>>> install scripts in framework/bin.
>>>>
>>>> OK.  Verified that we can create composer.json with his library:
>>>>
>>>> https://github.com/claylo/conductor
>>>>
>>>> On the command line, it works via:
>>>>
>>>> # php package2composer.php
>>>>
>>>> in the same directory as a package.xml file.  One caveat: this  
>>>> needs to be added manually to the composer.json file:
>>>>
>>>>  "repositories": [
>>>>      {
>>>>          "type": "pear",
>>>>          "url": "http://pear.horde.org"
>>>>      }
>>>>  ],
>>>>
>>>> (This can be done via a config file going forward).
>>>>
>>>> This will install all dependencies for a package using Composer  
>>>> (using PEAR packages).
>>>>
>>>> It seems that Pirum does automatically create compose repos when  
>>>> building the PEAR repo, so maybe we can take advantage of that in  
>>>> the future.
>>>
>>> I'm still confused how this will help with people using our split  
>>> git repositories. This will work against the released PEAR  
>>> packages, right? So, how will we help people manage the various  
>>> dependencies when using git? If I'm checking out git to get the  
>>> latest and greatest code to work against (or help develop), I'm  
>>> also going to want to be able to checkout the git repository of  
>>> all of it's dependencies, not the PEAR packages - especially if we  
>>> are in development of a new major version where we won't have any  
>>> PEAR packages released yet that are compatible.
>>
>> Composer is capable of building packages from Git.
>
> This is besides the point anyway.  Above I am discussing how we can  
> create composer.json files for all packages as an alternative to  
> PEAR installation.  It has nothing to do with git reorganization.   
> This is something that can be done TODAY.

Maybe, but the point I was making, and Jan has addressed, is still  
valid. Before we can split the repos, we need to ensure we can help  
developers manage the dependencies while checking out any of our git  
repositories. I guess the context of the email caused me to misread  
the point you were making about composer if it did not have anything  
to do with splitting the repos.
-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2200 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/dev/attachments/20130621/4395d79e/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6062 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/dev/attachments/20130621/4395d79e/attachment-0003.bin>