[Typo3-dev] Hey system extensions! Come back to the extension repository!! was: Re: indexed_search / EXT Rep?

[Kasper Skårhøj]

I'm actually indifferent regarding whether system/global extensions are in TER 
or not. Obviously there are drawbacks with both situations at the present 
time:

If they are in TER:
- we have to keep the extensions distributed in the core in sync with TER 
which is some 120 times boring administration, currently done manually.

If they are NOT in TER:
- No manuals available
- No in-between-releases updates from TER (only CVS)


What is the better?

The first scenario is known for a fact because it has been documented that for 
many years I haven't been able to keep the 80 global extensions updated in 
TER each time a new release was out. That was also confusing.


Any attempt to find the good middleway seems to result in a) either an 
extended procedure that implies administrative work for someone or b) 
development of automation scripts that could do it for us.


- kasper


On Tuesday 11 October 2005 15:08, Wolfgang Klinger wrote:
>  Hi!
>
>  On Mon, 10 Oct 2005, Michael Stucki wrote the following:
> > Why do you think it is confusing? You don't need to update indexed_search
> > through TER because your version already ships with the most recent
> > version available. If there would be a new version, then there would also
> > be a new typo3_src release.
>
>  It's confusing (or rather annoying) because
>     a) I get no hint about an extension called "indexed_search" if I search
> in the extension repository
>     b) I get no documentation
>     c) I can't update/change the version
>         (let's say I want to stay with my shiny TYPO3 3.8 but only
>          update this extension (and not the CMF itself))
>
> > If you have no clue... (see Joeys signature)
>
>  bla bla
>
>
>  bye
>  Wolfgang
>
>
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

-- 
- kasper

-----------------
Think future, not feature