[TYPO3-ect] lib/div & compatibility

[Franz Holzinger]

Hello Daniel,

> Hello Franz,
> 
>>> so the only solutions seems to be that we use special extensionkeys for
>>> every release of the framework.
>>
>> Yes, because the EM does not support 2 versions of an extension to be
>> installed at the same time. You cannot use div 0.0.12 and div 1.1.1
>> simultaneously.
>>
>>> * first release (=SVN branch01): lib 01 + div 01
>>> * second release (=SVN branch02): lib 02 + div 02
>>>
>>> Within a branch _NO change of the API_, just bugfix-updates.
>>
>> But additional functions and functionalities shall be allowed during
>> Alpha and Beta Phase. During beta phase only features from a defined
>> list may be commited.
>> Only bugfixes during RC phase.
> 
> An additional function _is_ an API-change :-)
> 
> Example: If lib02 and div03 are the current extensionkeys and they are
> in use for some extensions any new functions should go into a new branch
> lib03 and div03. Just bugfixes for already existing functions go in
> lib02 and div02.

This is bad. Imagine you are developing for div02 and then you want to
add a new function. Then this is so restrictive that you cannot continue
and must move to div03 which will take many months to get ready.
Or you must copy this code into all of your extensions. This is also bad.
This is only managable if div02 is already in RC phase. But it is too
restrictive during alpha and beta phase.

> The alias: We can do it as "package extension". "lib" has the dependency
> "lib02" and _NO code_ , same with "div".
> 
Do you mean something like PHK?
http://www.phpindex.com/index.php/2006/12/17/2695-phk-un-gestionnaire-de-package-pour-php


Or maybe the PHP Package Management?

http://jacwright.com/blog/40/php-package-management-and-autoloading/


- Franz