Hi Rene, >>> Or invent a nice solution that does auto-downloads, and switch a few >>> other huge external libs to that (like icu). ;)
Nice idea. > That would be a problem for some builders unless you don't download it > when the file is there... Sure. > For example, for Debian requiring any form of > net access on a build is a no-go (and for some libs we have to use the > internal versions, and be it sometime, in emergency) What's the definition of "build" here? I.e., between getting the sources (which most probably requires net access), and issueing the actual build command - where's the "no net access from here onwards"-line drawn? > And please also think on people bulding somewhere without net access.. Thorsten's PreReq-Cache could solve this. It would be needed, anyway - you dont't want to download the complete tarball for each and every build, if you do multiple of those. A slight modification of the idea: Instead of getting all the tarballs from <module>/download, get them from $OOO_PRE_REQUISITES. If they're not there, bail out (the same way you would bail out today when they're not in download). This means multiple source trees would share the same prereq-repository. Adding an auto-download could be a second step to this. Anybody volunteering to embark upon this? I'd say this would be a tremendous improvement, but I myself don't really feel competent to hack that deep in the OOo build environment. Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
