Egon Schmid wrote: >>we are talking about eventualy splitting it even more >>as some of the files are getting big enough so that >>you get lost when trying to edit them or when you >>attempt to track the changelog for these,
> Please don�t make such megapatches. If you split the languages into > different repositories, do it in single steps. i'm afraid you are mixing up things here we currently have three different 'split' topics 1) the "installation/configuration" split 2) the "cvs/one repository per language" split 3) the "function level/translation granularity" split we've already done part of 1), although it is not perfect yet but no big patches will result from the work left to do 2) will require some preparation on the server side, but for the clients it will be rather easy if you are lazy you can just update your cvs after the split is done and all translations will be gone, if you need one or more of them you can do a fresh checkout of these from within the phpdoc dir if you do not want to waste time and bandwidth you can apply a small shell script that will rewrite the Repository files in all the translations CVS subdirs to reflect the changed file positions on the server if we just create new repositories on the server and move the CVS *.xml,v files to these new directories we will have exactly the same version numbers, file contents and history entries as before, so that a cvs update done immediately after the switch and after the rewriting shell script has been properly applied will not transfer any data at all as the same changes have been applied on client and server side we can even provide a tar.gz or zip file containing the new Repository files for those platforms where no shell exists or for those who do not trust it 3) will cause a lot of changes to the repository. if i get my current plan to work it will even completely get rid of the 'functions' subdir and will replace it with a 'reference' subdir that will itself contain one subdir per extension/reference chapter. but this is all still experimental, i'll publish a conversion script as soon as i get the complete split conversion working without human intervention so that we have some fakts to discuss about before i even think about how the final solution might look like it might even be that someone comes up with a clever solution to solve the problem on the xml level and not on the file level anyhow, no patch will be done in this direction until it is very clear that the concept really works and is scalable but *if* a change requires a patch, no matter if it is a big or small one, it should be done in *one* step and not in a series of smaller ones just to save the bandwidth as it is rather hard to split a change into several pieces -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
