[dev] Install script ideas

[Jan Schneider]

Zitat von Barsalou <barjunk at attglobal.net>:

> Jan said:
>
>> IMO, the script first should bootstrap itself similarly to the go-pear
>> script by getting the necessary base classes from the CVS server via HTTP.
>> It should then check the system, similar to test.php (and probably using a
>> common set of test, no idea yet how to implement that though). If necessary
>> it should offer to install PEAR, necessary PEAR packages, and upgrade
>> existing PEAR packages.
>
>> After requesting the necessary information from the user it should download
>> and install the tarballs, create the configuration files, run SQL scripts.
>> It might be a good idea to run application-specific tasks by calling setup
>> scripts bundled with the applications.
>
>
> I like the idea of having an install script that each application 
> uses to do the
> install for the module.
>
> I'm not sure what are considered the base classes.  Are they in the 
> horde tar?
> Is it only the framework stuff?  Isn't the framework included in the horde
> "production" tar?

Yes, but we don't have the tarball when we start the installation script. At
least that's what I meant. But now that I think of it, we could as well
first download the latest horde tarball and start from there.

> Do we really want to be using CVS?  I guess that would provide the latest
> changes.

If we need to bootstrap anything before we download the tarball and don't
want to include the bootstrapping code into the install script, yes. That
doesn't mean that we need a CVS client, I was thinking along the lines of
"include 'http://cvs.horde.org/co.php/horde/lib/Test.php';"

> We could use the naming convention that is currently being used 
> namely the "h3"
> part, instead of a seperately maintained list of available modules.  
> Something
> that signifies production versus beta, etc.

That still doesn't get us the list of available modules, and browsing
through the whole FTP server is not an option.

> How about adding a new status in the Administration->Setup screen, like
> "application not installed"?  Maybe follow that with an info link and 
> an install
> link?

That could perhaps be done in a later step. At the moment we don't even get
a basic Horde installed.

> The info link would display a short bit about the application.  The 
> install link
> would go get the "production" tarball and do the things it needs to do
>
> We can load the framework initially, and it will provide access to the
> configuration screen.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/