> > Notes: - Have a separate section on where to get the source?
>
> If you're talking on an extension basis, I think we should only
> link to http://pecl.php.net/extname from reference.xml, this page
> contains a list of all available releases of extname.
>
> If not, please clarify your question for me :)
There are several places:
a) pecl.php.net
Ideally all downloads will exist here but this isn't the
case. Windows users must look elsewhere, and not every
PECL extension has such a page. Related bugs:
Will there be information for Windows users?
* http://pecl.php.net/bugs/bug.php?id=2008
Will these missing PECL extensions be integrated?
* http://pecl.php.net/bugs/bug.php?id=2109
b) DLLs: php.net/downloads.php and snaps.php.net
c) CVS
d) pear
If I were installing it statically I'd suggest doing something
like: pear download extname
But let's assume eventually all PECL extensions live at pecl.php.net,
and that all DLL's will be linked to from there. It's still nice to
provide information on where to get these files as many other options
exist.
> > -----------------------
> > General Considerations:
> > -----------------------
> > PHP extensions may be installed in a variety of ways. PECL is a
> > repository of PHP extensions living within the PEAR structure,
> > and the following demonstrates how to install these extensions.
> >
> > The source of these extensions may be found at pecl.php.net or
> > to retrieve from CVS use:
>
> I'd write : "or retrieved from CVS using:"
Sounds good.
> > In case the preferred_state differs, like it's set to stable and
> > the extension is still in beta, either set the preferred_state
> > via "pear config-set" or simply specify a specific version of
> > the extension. For example:
> >
> > $ pear install extname-0.1.1
>
> Here you're using the word "preferred_state", which you didn't
> introduce, it may be confusing for someone trying his first install.
>
> What about this? <<<EOD
>
> In case you want to install a different state of the extension, either
> set the preferred_state option via "pear config-set" or simply
> specify a specific version of extname. For example:
>
> $ pear install extname-0.1.1
>
> EOD;
I agree it could be worded differently but disagree with your
reason. The introduction will link to information on using the
pear command but it's not our worry here. I can't find this
sort of information in the PEAR manual but ideally something
like the following will exist soon:
http://www.phpconsulting.com/pear.php
Let's add this type of information to peardoc so we may link
to it. Also I've been trying hard to avoid using "you", and
this was difficult here...but that's another topic :)
> Will we link to this page from reference/extname/reference.xml ?
> Also, can Windows users build an extension in their own ?
> We also need to have the Windows instructions if they do.
One of the PECL entities should link to it. Either pecl.info
or a new one.
I don't know about Windows users who choose to compile their own
DLLs but I'm sure this information can be added later. I assume
a very small number of people do this.
> Nice work Philip !
Thank you :)
Regards,
Philip
