On 18 Dec 2008, at 07:15, DeDe Morton wrote:


hannes.magnus...@gmail.com wrote on 12/18/2008 03:35:53 AM:

> On Wed, Dec 3, 2008 at 19:22, Olivier Hill <oh...@php.net> wrote:
> > On Wed, Dec 3, 2008 at 12:47 PM, Philip Olson <phi...@roshambo.org> wrote:
> >>
> >> Ahh! Each extension now contains its own versions.xml* file whichdeprecates > >> phpbook-xsl/version.xml although the latter is still used today (the move
> >> isn't yet complete). The two have now been synced.
> >
> > Really?!?! Thanks Philip, I'll update my documentation. I was
> > wondering why some PECL functions were documented with: "No version
> > information available, might be only in CVS".
> >
> > The file isn't auto-generated in some way right? I can modify it
> > freely inside the module directory?
>
> Its not autogenerated no.
>
>
> -Hannes

(Sorry if you receive a separate posting from me about this today...my mail server is sick.)

I need to clean up phpdoc/en/reference/ibm_db2/versions.xml. However, the entries aren't in sync with the entries in the version.xml file. Should I take the entries from version.xml and paste them into my extension-specific file? For example, the version.xml file says <function name="db2_autocommit" from="PECL ibm_db2:1.0-1.6.2"/>, but the versions.xml file says <function name='db2_autocommit' from='PECL ibm_db2 &gt;= 1.0.0'/>. Is there a preferred format?

While splicing up version.xml to individual versions.xml I secretly changed the format so we won't have to update the version files with every new PECL release. And it's now more like the rest of the documentation now.

Also, when will the change over to extension-specific versions.xml files take place? I thought this was happening last week, but the pages I'm looking at still reflect what I see in the version.xml file.


A new release of the build system (PhD) hasn't been released yet, however, the developmental box is using it from CVS:

    http://docs.php.net/manual/en/function.db2-autocommit.php

I'm guessing a new release will take place soon, so either this or next Friday the new version information will be online. Also note that {ext}/versions.xml information takes precedence over the monolithic version.xml file.

Regards,
Philip

Reply via email to