I don't disagree with that. G is pretty easy to build. It's just a chore downloading upto 4 different prereqs from 4 different locations. But I see your point reg. SDK.
Thanx
Prasad
On 11/2/05, Barry van Someren <[EMAIL PROTECTED]> wrote:
We could not ship the SDK (which is required to build the code) but we
could in theory ship the others.
You'd still need to worry about integrating them into the OS though,
so I'd suggest we just keep pointing the users to instructions for
CVS, SVN and Maven.
It's a pain to set up, but most developers will either already have it
or will know how to install it (with or without the instructions)
Once you have everything setup, G is one of the easiest environments
to work with.
On 11/2/05, Sachin Patel < [EMAIL PROTECTED]> wrote:
> -1 from me. I could possibly understand the JDK, but definatley not
> svn, maven, and CVS.
>
> Prasad Kashyap wrote:
> > This may be slightly related to Hernan's wiki thread but since we were
> > talking about G for the impatient and a newbie manual, thought I'd ask this.
> >
> > Dave Klavon was talking about a single download and setup of all
> > prereqs and G source, and build it too. I liked that idea and think that
> > would be really nice. I even put together a package with basic scripts
> > for that.
> >
> > However, now I am beginning to wonder if it is legal/permissible for us
> > to "/ship/" JDK, svn, maven and CVS in this single package ?
> >
> > Comments ?
> >
> > Cheers
> > Prasad
>
> --
> Sachin
>
