[TYPO3-ect] "package extension"

[Daniel Pötzinger]

Christian Welzel schrieb:
> Daniel Brüßler schrieb:
> 
>> Just the emconf-file is needed with the list of all dependencies,
>> nothing else. When an admin installs the package-extension the extension
>> -manager gets all sub-parts.
> 
> The problem i see here, is that such an extension might pollute the
> typo3 installation it is installed in. Example:
> The package ext "lib" depends on some exts, that make sense for the
> programmer of a new ext "foo" so he depends on "lib" and not on the
> parts he only uses (lib_template_html, lib_pagebrowser). All is fine
> until now.
> Now Elmar comes in and thinks "lib" should also depend on 6 other
> lib-extensions (propel, squid-proxy, rss-import, you get the idea) and
> adds these dependencies... so the EM pulls in all new extensions on an
> update of lib although the only extension that uses lib ("foo") doesn't
> need them...

I think this is not what Daniel means.
Of course lib should not depend on much other extensions, cause it has 
relevant classes for other extensions.

But we can have an extension "lib_package" which depends on
lib / xajax / ...
But this is what Elmar creates with the ect extension.

So everything is perfect now I think?