mscharkow at gmx.net
Fri Apr 15 12:17:22 CEST 2005
Kraft Bernhard wrote:
> I have an idea for another solution for a TER than a filebased.
> A CVS based.
> It would be possible to create a T3 extension which controls a CVS
> server via the cvs commandline client and is doing all import, update
> and checkout commands when a extension gets registered, uploaded and
Okay, I'm dumb, but what's the point in doing this? End-users don't care
about version control but only about releases. Developers can do the
version control themselves, and even if we offer server-side
repositories for CVS or subversion. Why add another wrapper around it
and not use plain cvs or svn?
I could imagine a CVS/subversion import for extensions, so you can map a
repository URL to an extension, and in the backend say: Check stuff out
from XYZ and make a release out of it. So that I don't need a T3
installation in order to upload stuff to TER.
> It would save a lot of space and is easily maintainable, possible ot
> backup and it could by mirrored by simply doing an rsync of the CVSROOT
Mirroring just plain t3x-Files ist even simpler and I am not too worried
about space issues because harddisks and bandwidth are cheap.
> If an extension exists which interfaces T3X to CVS it would be possible
> to build the main TER site extension on it which is responsible for uploads
> and all the other TER mirror sites which are just for download.
This is planned anyway, as we will have on master repository for uploads
and a lot of whatweretheycalled? servers for download. I'd rather not
dynamically check out stuff from CVS because this causes load and I
don't see advantages in doing it.
More information about the TYPO3-team-typo3org