>>    Should the dev manual have it's own CVS repository with it's own
>> build system? Probably not for the first time. I think it may go
>> into phpdoc/devmanual/* and if it grows to something reasonable,
>> then it should go alone.
>
> Any technical reasons to NOT have an own module in CVS and
> similar/adopted/ported (whatever) buildsystem?
>
Maybe I'm just in crazy land here, but isn't the developer's manual
ALREADY in its own CVS module? "ZendAPI"

Note: Not to be confused with phpdoc/en/appendices/phpdevel.xml which is
all PHP3 development documentation and should *probably* be taken out of
manual.xml.in as it's WAY too old at this point.

>>    This also means that the build system needs to be extended to
>> choose what manual you would like to build (in the configure step).
>
> IMHO in genaral I suggest a solution that allows an easy and
> maintainable way  of splitting and building, regardless of having an own
> module/buildsystem or  not. The pragmatic way for me: if ist easier to
> tweak the current buildsystem  we should go this way....
>
I vote for a truly separated build process.  Instead of phpdoc having a
./configure option "--with-zendapi".  Give the ZendAPI manual its own
configure/build process for creating a WHOLLY SEPARATE manual.  And to
avoid search conflicts and general confusion, make a separate website for
it. http://dev.php.net perhaps?

I know this is no small undertaking.  The general website would have to be
built, the www.php.net url search would have to be adapted to the
developer manual search, and *most importantly* many <linkend> references
in the current user *and* dev manuals would have to be fixed to properly
cross-reference between sites.

I'm willing to put in some of the work.

>> Here are my thoughts. It is important to make up an RFC of this, as we
>> discussed, so the results will stay at some place, and there would be
>> no need to restart this again, and again...
>
> +1, I am willing to spent  some time to gather the suggestions from this
>  thread and put a starting doc in RFC.
>
> I suppose the php3 related dev stuff should also moved?
>
*re*moved maybe?

-Pollita



-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to