Re: cvs: phpdoc /en/reference/ssh2 installation.xml
| From: | Philip Olson | Date: | Wed, 02 Mar 2005 06:11:12 +0000 |
| Subject: | Re: cvs: phpdoc /en/reference/ssh2 installation.xml | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969366802@lists.php.net to get a copy of this message | ||
> > Why does the ssh2 PECL extension have its own complete
> > installation documentation? Rather then duplicate this
> > information for every extension it would be nice to expand
> > the installation.pecl docs to cover more, and refer to it,
> > and only include extension specific information in
> > installation.xml
> >
> I agree, I had several dozen users prompting me for installation
> instructions though and rather than hash out a meaningful solution like
> you're alluding to, I just solved the "right now" problem.
>
> I'm all for working up a Grand Unified Installation document and trimming
> out ssh2's installation.xml when the time comes.
Some differences between ref.ssh2 and pecl install
instructions thus far:
** Windows users:
None except install.pecl.windows should link to the
install.pecl.downloads section. So installation.xml only
needs to mention the required dll names.
** Linux:
* Where to get the external libraries and which are
required:
Right now pecl.php.net/ssh2 refers to libssh2 as a
requirement but does not mention openssl. Who's job is it to
say which external libraries are needed and where to get
them... is it php.net or pecl.php.net or both?
* Installation instructions:
The install.pecl docs describe all methods described in the
ref.ssh2 docs:
pear installer
phpize
The install.pecl also descibes static.
** Everything
Right now install.pecl covers everything but ref.ssh2 makes
some points clearer so install.pecl can learn from that.
Like:
How to edit php.ini to include the shared (.so) file, and
that this is affected by the extensions_dir directive.
Although pecl.install.pear mentions preferred_state, it
could further describe what this means and how to tell which
options are available. For example ssh2 only has beta
available at this time. We don't need a lot of detail on
this and should refer/link to the pear manual for detailed
explanations.
Restart web server.
Whether a new install.pecl section is needed that descibes
how to finish the install process (move .so file, edit
php.ini, properly set extension and extension_dir, restart
web server) I'm not sure. Windows, shared.pear and
shared.phpize could all refer to this new section as the
last step.
What do you guys think? :)
Regards,
Philip