Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of peter.hunsberger@gmail.com
 designates 64.233.184.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=QTtIKUOqgiISMmAFBvBO3JkAhnCTcaeno8PmO8+Urxh8hrho2aOjL28MLqC/OFeyWwBwgpCKz2Uk0l+1qlalziYIJm8qfjrFRWXilmL+Rpnac+JdYkRjhtdMrRC2JzhCf4jPkWcaoZlZbXS4MDMDm81iPL74JNT6n2286GH1Wig=
Message-ID: <cc159a4a05041411432ec2185d@mail.gmail.com>
Date: Thu, 14 Apr 2005 13:43:08 -0500
From: Peter Hunsberger <peter.hunsberger@gmail.com>
Reply-To: Peter Hunsberger <peter.hunsberger@gmail.com>
To: dev@cocoon.apache.org
Subject: Re: Do we want a GUI installer?
In-Reply-To: <425EB698.1060706@upaya.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200504141751.j3EHpcjM009769@mira.taygeta.com>
	 <425EB698.1060706@upaya.co.uk>

On 4/14/05, Upayavira <uv@upaya.co.uk> wrote:
> Skip Carter wrote:
> > I'd rather not see one.  At least if one is developed,
> > there needs remain to be a way to install from the command
> > line.  ALL of my cocoon installations are on headless systems,
> > and some of them are remote, so a GUI is not really very practical.
>=20
> There is no way that such an installer would replace the current system,
> merely augment it. This installer is nothing more than a wrapper around
> our existing Ant scripts anyway. After all, many Cocoon installations
> are on headless servers. The intention was to smooth over that early
> stage of usage when someone is at the beginning of learning Cocoon.
> Throwing them into having to copy and edit text files when they first
> start IMO introduces complexity that they could well do with learning a
> little later in their involvement with Cocoon.
>=20
> But, having said that, it doesn't seem like people are that keen on the
> idea anyway.

I think without the license problems people might be in favour or
least neutral.

Perhaps you could include the config script with Cocoon with a pointer
to the Source Forge project?  Alternately, maybe you could donate the
config file to the Source Forge project and include something in the
Cocoon docs...

--=20
Peter Hunsberger