on 8/28/2000 9:40 AM, "Daniel L. Rall" <[EMAIL PROTECTED]> wrote:
> -1, the TDK should be in it's own repository. +1 on moving it into the
> tdk repository.
Yes. I agree with Daniel, but let me expand on that.
The idea behind the TDK is not to necessarily store a lot of stuff in it. It
really is its own product that happens to depend on Turbine as well as a lot
of other tools. The TDK is simply a set of scripts that is responsible for
building a distribution that developers can use. Thus, there should not be a
lot of duplication between the TDK and Turbine...it should simply pull what
it needs out of Turbine and other stuff and use that.
What the developers should end up with inside the TDK is the following:
A distribution of Turbine
A distribution of Tomcat
A distribution of a Java database
A distribution of a few sample applications for Turbine
Tons of documentation.
All of this should be pre-configured to run by simply executing one single
script and then going to a URL to see it in action.
Now, the process of building the TDK from scratch should be something that
only a few people ever have to know or care about. This means that it does
not necessarily have to be an easy process (ie: it might have a lot of
pre-requirements), but it should definitely be documented and possible to do
cross platform as well as being scripted as much as possible.
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
