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 :)
[plop] 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.
So we need another section, with the different places you mentionned
and a good description for each one. The text under "General Consideration" and the other parts of your proposal explaining how to
checkout the sources (when you're explaining how to get them from CVS
for example) should be substituted by a link pointing to this
information.
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.
It should be there:
http://pear.php.net/manual/en/installation.cli.php
I'll propose a patch to peardoc (if you didn't already).
Also I've been trying hard to avoid using "you", and this was difficult here...but that's another topic :)
heh :) sorry!
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.
What are those entities ? Do you already have a list that needs a review ?
In a side note, I remember a discussion about two kinds of manual builds. One including PECL extensions docs and one without them.
Was I dreaming or is this really on the TODO list ? (if so, I already started cooking a patch that adds a --without-pecldoc to ./configure
and hacks manual.xml on the fly just before starting the build.)
Regards,
didou
