[TYPO3-dev] Poll: Should we keep supporting "global extensions"?

[bernd wilke]

Am 13.12.14 16:42, schrieb Ivano Luberti:
> Hi Ben, I'm glad that once again is confirmed how good open source
> approach is in software development.
> However I would like to add a few notes (not really complaints, only
> notes :-) )
>
> First I believe that the dev list was not the proper place where to
> conduct this survey: it is more a system administrator thing and many
> TYPO3 developers don't have much of a relationship with those figures. I
> bilieve that the TYPO3 users list would have been more appropriate.
>
> Second, while I'm in favor of a maintaining this features I believe that
> in order to make it useful at least two conditions should be respected:
>
> 1) if I can define one or more storage locations on a server for global
> extensions there should be a single point of administration for it in
> order to upgrade version or remove extensions
>
> 2) in every single TYPO3 instance there should be a way to specify if an
> extension has to be installed from the the local server storage or from TER
>
> Finally if it is decided that global (with respect to a server)
> extensions have full dignity some rules/conventions on how to develop
> extensions should be changed: for example extensions can be configured
> from extension manager but value are taken/written from/to
> ext_conf_template.txt , a file local to the extension folder that for a
> global extension would be shared among different TYPO3 instances.
> I believe that a web based extension configuration interface like  the
> one  provided by the EM should remain available but then how to handle
> this shared config issue?
>

just some thoughts coming to mind:

if we can share TYPO3-sources (of different versions) from a global 
place by symlinks, why not do it the same way with extensions?

there could be a global space for extensions of any kind and versions 
(something like a local TER) and each installation can symlink the 
appropiate extension(-version).
further special-versions may possible like some provider do automated 
updates for insecure extensions anyway:
have links to latest version and latest security update.

in this way each installation can have access to global extensions and 
beside have a space for private extensions (modified TER-extension or 
individual private). this also would be the default for extensions 
installed from TER in the EM)
and: the handling inside TYPO3 could be simplified as there is only one 
folder with extensions.

bernd
-- 
http://www.pi-phi.de/cheatsheet.html