Am Donnerstag 23 Januar 2003 12:06 schrieb Gabor Hojtsy: > Hi! > > I am opening this up as a new thread, so we can start in a clean > situation to discuss only this problem.
once again ;-) [...] > 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? > 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.... > 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? -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
