[TYPO3-ect] "package extension"

[Christian Welzel]

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...

The same problem is known from debian, where you as package maintainer
has to carefully choose the packages to depend on, not to force the user
to install the whole kde only because you depend on such a "package
packge".

Bye Christian.