On 21 February 2011 08:01, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: > On Fri, Feb 18, 2011 at 18:06, Richard Quadling <rquadl...@gmail.com> wrote: >> >> The all.bz2 file only contains 1 file called 'all'. >> > > > Is it actually still being generated? I suspect that it may no longer > be the case.. > > >> And that file has to then be chopped up by PHP to make it useful. >> >> Or does the rsync process copy an uncompressed usernotes directory? > > That depends on what rsync process you mean.. > > The CHM generation happens on oti1.php.net, which only has a checkout > of phpdoc-all > The user notes would be fetched from your local neighborhood mirror > /backend/notes.bz2 if its still being generated. > > > After the chm build has been finished the file gets copied to > rsync.php.net, then a quick sanitycheck of it is done before copied > into the proper rsync space for mirrors to retrieve. > > -Hannes >
http://www.php.net/backend/notes/ seems to be updated every 2 hours. If /backend/notes/xx is rsync'd then there is no need to deal with bz2 at all. In looking at the build-chms.php script, I see that every language is built and then the output directory deleted, ready for the next language. As the user notes are not language specific, they should be outside of this setup, but there is no way to do that cleanly/safely without being allowed to define a path on the command line. To that end, I'd like to propose a small change to PhD and the role of --output-dir. Currently ... phd\render.php --output-dir=C:\Output -P PHP -f chm -f enhancedchm will create content like ... C:\Output\index.sqlite C:\Output\php-chm C:\Output\php-enhancedchm Adding --lang=xx will make no difference to the output. My proposal is that the output directory will automatically include the language as a subdirectory. So, making ... C:\Output\en\index.sqlite C:\Output\en\php-chm C:\Output\en\php-enhancedchm With that, I can now use Config::output_dir() . 'usernotes' as a predictable location. C:\Output\usernotes\all.bz2 C:\Output\usernotes\all C:\Output\usernotes\last-updated C:\Output\usernotes\usernotes\xx I'd also be making phpdoc/configure.php output to a language specific filename. So, currently, build-chms.php has ... execute_task('- Configure', PATH_PHP, PATH_DOC . '\doc-base\configure.php --disable-libxml-check --with-php="' . PATH_PHP . '" --with-lang=' . $lang . ' --enable-chm', 'configure_' . $lang); By using ... execute_task('- Configure', PATH_PHP, PATH_DOC . '\doc-base\configure.php --output=.manual-' . $lang . '.xml --disable-libxml-check --with-php="' . PATH_PHP . '" --with-lang=' . $lang . ' --enable-chm', 'configure_' . $lang); (and this would continue through the build-chms.php script, essentially adding $lang to the file and directories in the appropriate places). Is this reasonable? Or a problem? As the final CHM file is always language specific in the filename, I can't see any issues with this as it is only a build process change. I have to have some way of identifying the location of the usernotes, I don't want to hard code a relative path as I don't know where the output will be. Richard. -- Richard Quadling Twitter : EE : Zend @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY
