[horde] Extending horde modules

[Jan Schneider]

Zitat von Marko Djukic <mdjukic at horde.org>:

> Quoting Jeff Lindsay <progrium at gmail.com>:
>
>> I've been playing with and reading about Horde for a while and I
>> really love it. I'm about to start an internal project at work that
>> will use Horde to replace our current, proprietary, out-of-date, pos
>> system, which will require adding new modules and modifying current
>> modules.
>>
>> We're going to be using CVS during development, which is something I'm
>> fairly new to, but look forward to working with. My question is what
>> do you guys think is the best way to go about setting this up?
>>
>> First, what's the best way to deal with Horde community commits to
>> modules we'll be extending? It seems a little dangerous to be
>> committing our own changes to our local CVS as well as changes made by
>> the Horde community on that module, besides the complexity that would
>> seem to involve. Would this even work?
>
> propose the modules and see what the reaction is for including them 
> into horde's
> cvs.
>
> otherwise keep your own modules on your cvs, and any mods to the existing
> modules just send as patches to the dev@ list. your own development setup can
> easily sync from both sources.

And if you really need to track your changes to Horde's code in your own CVS
while still being able to update from our changes, you need to use vendor
branches in CVS (see Cederqvist).

Jan.

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