[Typo3-dev] tstemplate extension and EM version inconsistencies

[Stephane Schitter]

Selon Kasper Skårhøj <kasper at typo3.com>:
> you are right.
>
> Where version numbers doesn't match up: Mostly because uploading 70
> extensions each time I release the core is a lot of work - so I don't do
> it.
>
> And I'm sorry about that.
>
> We are currently restructuring some stuff which will also consider a
> consistent flow for this in the future.
>
> - kasper
>
>
> On Wed, 2004-05-05 at 18:19, Stephane Schitter wrote:
> > Hello,
> >
> > I have come across a strange problem today -- I was following the "Inside
> Typo3"
> > core installation of Typo3, and I went from that state into installing some
> > basic extensions as "Local" extensions.
> >
> > All went well, but when I came to install "tstemplate" I noticed weird
> > behaviours with a function rtw() not being found.
> >
> > A dig into the php code (around line 251) showed to me that it should
> actually
> > be template::rtw() that should be called, but then that led to other
> strange
> > behaviours and...
> >
> > ... this is the point where I noticed that tstemplate from the TER seems to
> be
> > older than the tstemplate shipped with Typo3 3.6.0  -- even though they
> share
> > the same version number "0.0.4".
> >
> > Am I wrong here ?
> > and if not, where would the latest tstemplate be ?
> >
> > This is not the only post where revision number on TER vs. CVS versions are
> a
> > problem and confuse people, but in this case there isn't even a tstemplate
> CVS
> > version it seems.


I am a great believer in the smallest core and have the most basic install be
the standard. I remember seeing discussions on the ideal situation being where
Typo3 has all extensions as local, and none global by default (except maybe the
"install").

If that were the case (in an hypothetical future), then the maintenance of the
extensions would not need to be inline with the core (unless a feature in the
core ties to the release of a new version of extensions).

What is the reason for not slowly phasing out global extensions ?
- admins not knowing what to do when they upgrade and discover (or not...) that
usual extensions are not in the core anymore ?
- being too much of a pain when even basic extensions like tstemplate, etc...
need to be installed as local and not have an out-of-the box solution ?
- any other ?

I have not been a typo3 user for a long time (few months now) but I've started
converting my install(s) towards an almost empty typo3/ext directory and have
all but a couple of extensions in typo3conf/ext of the individual sites.

Stephane