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

[Jo Hasenau]

Am 08.12.2014 17:43, schrieb Philipp Gampe:
> Hi Martin,
>
> Martin Wiederkehr wrote:
>
>> We widely use this feature to provide specific global functionality
>> without changing the core. Of course, this could be done also in every
>> project repository, but then there is no way to rollout a security patch
>> to every installation in a minute.
>>
>> This works pretty well for us as we also maintain a centralized TYPO3
>> source which is used on every hosting of us. Therefore this would be a
>> real drawback if the functionality would be removed.
>
> Why don't you use a symlink inside the typo3conf/ext/?
>
> This is how I share extensions across installation. Also, there is no way to
> mess up with a local and a global extension.

Actually this would be the reason why I would prefer to keep it.
The cool thing about the system => global => local concept is, that you 
can even decide, on which level the user of the system is allowed to 
install and/or edit extensions. (Although editing does not work with the 
current EM anymore)

So while the system extensions are provided by the core team and the 
global extensions are just a pool of useful stuff that you (i.e. as a 
hoster) provide for your clients, each of these clients can override 
these default extensions by installing a local version with a different 
code base.

And you need to change just one symlink to from typo3/ext to your pool 
instead of having to create a symlink for each extension.

So +1 for keeping global extensions.

Cheers

Joey

-- 
Diversity:
Die Kunst zusammen unabhängig zu denken
The art of thinking independently together.
--
Facebook: https://www.facebook.com/johasenau
Twitter: http://twitter.com/bunnyfield
Xing: http://contact.cybercraft.de
TYPO3 cookbook (2nd edition): http://www.typo3experts.com