kde-svn@midna /kdesvn/src/extragear/utils/kdesrc-build $ kdesrc-build -p --rc-file kdesrc-buildrc-sample Would have created /home/kde-svn/kdesrc * ACTUALLY downloading projects.kde.org project database to make the rest * of the --pretend output make sense. Encountered an error in the execution of the script. The error reported was Couldn't open /home/kde-svn/kdesrc/kde_projects.xml: No such file or directory at /kdesvn/src/extragear/utils/kdesrc-build/kdesrc-build line 1015 at /usr/lib64/perl5/vendor_perl/5.12.3/x86_64-linux/XML/Parser.pm line 219 XML::Parser::parsefile('XML::Parser=HASH(0x2649d00)', '/home/kde-svn/kdesrc/kde_projects.xml') called at /kdesvn/src/extragear/utils/kdesrc-build/kdesrc-build line 1015 KDEXMLReader::getModulesForProject('KDEXMLReader', 'automoc', '/home/kde-svn/kdesrc') called at /kdesvn/src/extragear/utils/kdesrc-build/kdesrc-build line 6063 main::__ANON__('Module=HASH(0x2933040)') called at /kdesvn/src/extragear/utils/kdesrc-build/kdesrc-build line 6105 main::expandXMLModules('ksb::BuildContext=HASH(0x2905dd0)', 'Module=HASH(0x2921280)', 'Module=HASH(0x277bc10)', 'Module=HASH(0x2933040)', 'Module=HASH(0x2933340)', 'Module=HASH(0x29334f0)', 'Module=HASH(0x29336a0)', 'Module=HASH(0x2933850)', 'Module=HASH(0x2933460)', ...) called at /kdesvn/src/extragear/utils/kdesrc-build/kdesrc-build line 8282 eval {...} called at /kdesvn/src/extragear/utils/kdesrc-build/kdesrc-build line 8188 Please submit a bug against kdesrc-build on http://bugs.kde.org/ Don't forget to fix it... ;)
Git commit 2fb6687becd8f1f5b4797e40edc2812e9a4ee151 by Michael Pyne. Committed on 12/03/2012 at 03:16. Pushed by mpyne into branch 'master'. Fix handling of kde_projects.xml on first-run. Specifically, on first run in --pretend mode, where kdesrc-build has no existing metadata of any sort downloaded, and no way to make a source dir to hold incoming metadata. Instead we just save it in a temp file. The kde-build-metadata module still doesn't get downloaded though, and so if you (for whatever reason) run kdesrc-build --pretend as your first action upon installing kdesrc-build, you would not get 100% accurate build plans. Instead of special-casing that I think I would just add a --init or --setup command line option and then tell the user to use that for "--pretend in first-use" scenarios. M +31 -13 kdesrc-build http://commits.kde.org/kdesrc-build/2fb6687becd8f1f5b4797e40edc2812e9a4ee151