[TYPO3-ect] lib/div & compatibility
Franz Holzinger
franz at fholzinger.com
Mon Apr 28 07:08:49 CEST 2008
Hello Daniel,
> if we provide an upgrade-guide from one version to the next the problem
> is solvable.
>
> So it's no problem that just one version of lib and div can be on the
> server. In the PEAR world it's easy to check WHAT version an installed
> class has, but just ONE version of a package can be on the server. In
> the Java world it's the same. A jar has a versionnumber, but when it's
> in the classpath just one can be active.
>
> =>
> 1. We need an upgrade-guide and so a fork "2007" and so on is not in need
> 2. The version-number of lib and div should be better:
> <major>.<minor>.<bugfixes>
>
> Until now just the bugfix-number was increased, but in reality the API
> was changed all the time.
>
> Wouldn't that solve the problems?
No, this would not help very much. There will be several extensions
depending on different versions of div.
But you can only install one version of div at a time. And you want to
use all those extensions at the same time. All versions must be active
at the same time or you will have to wait until all those extensions are
available for the same version of div. And then there will be an update
of one of those extensions again using a changed API. So this is not
managable. The TYPO3 admin would have a lot of stress to get something
working.
- Franz
More information about the TYPO3-team-extension-coordination
mailing list