[dev] Git splitting

Michael M Slusarz slusarz at horde.org
Fri Jun 21 22:24:12 UTC 2013


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

> 1. User running their production version of horde from a PEAR install.
> 2. User discovers Horde_Core issue.
> 3. User downloads the git repo for Horde_Core anywhere they want on  
> their system.
> 4. User configures autoloading to point to the Horde_Core directory  
> they want to use instead of the global Horde_Core  
> (horde/config/horde.local.php would be a place to allow this).
>
> Done.  There cannot possibly be an argument that this is more  
> difficult than the current process.

Additionally, #4 is not even necessary in most cases.  This is how  
pretty much every single other software project works.  There's no  
need for more complex environment setup.  Need to test it?  That's  
exactly what unit tests are for.

Switching over to an application repo is slightly more complicated in  
that you will have to copy config files and ensure that the app  
directory is web accessible.  But that's it.  (Step #4 above would be  
replaced with changing the application path in the registry).

michael

___________________________________
Michael Slusarz [slusarz at horde.org]



More information about the dev mailing list