> > > Another thing I was wondering. Why not make a clean break right now? > > That is, let each project have its own version of the common source that > > gets checked in today? Then they can be maintained independently. > > DRY principle! (don't repeat yourself) > We should not have redundant code in impl and tomahawk, right? > > > Manfred > >
Thanks for the reply. Now I have a little more confidence that I understand what is going on. I'm with you for everything except maybe the adherence to the DRY principle. I'm not sure if it applies in this case. In a single system, DRY is very important. However, we are talking about two very different software systems - core and components. What happens when tomahawk needs to make changes to common that core doesn't need? Ideally, this stuff would be moved out of common and into tomahawk proper, but we know that over time this will not happen. Instead, small, seemingly harmless changes will be made that do not benefit both projects. A little core-specific stuff here, a little tomahawk-specific there, and soon you have a single code base with divergent purposes. I think we should go for another principle: simplicity. Let's make a clean break so that core and tomahawk can each fully go their own way. It might mean some redundancy now, but I think it will be much simpler for both projects in the future. Stan
