Hi Thomas, thanks for your passionate yet clarifying post - let me point out I didn't state that qooxdoo had it wrong, just that I have yet to understand why the simple approach should be discouraged, at least as long it is supported, for local testing and development, for example for newbies who want to test the framework.
thron7-2 wrote: > > in the case of contrib libs referenced with the "contrib://" pseudo > protocol, that means your download path has to be reachable from your > web server in the above sense, and pointing the CACHE config macro into > your source tree is a *very coarse* approach to achieve this. the > download path can just as well be the default location > (<system-tmp-dir>/cache/downloads), but can be any other path if you > adapt the config key "cache/downloads" for your build jobs accordingly. > the *compile* cache has nothing to do with it, so there is no need to > shuffle it around (which you do when you change CACHE). > To summarize points that were made on this thread and prevent future rumours :-) - the file:// approach doesn't work well with backends (Derrell) - configuring Apache to serve from unusual locations is possible but not easy (Derrell). - to start off with qooxdoo and a backend for local testing development (not production of course), there is an easy solution that does not require fiddling with Apache config files, but simply put the cache into the DocumentRoot (Christian), - however, this is discouraged by the qooxdoo dev's because it might not be supported in the future (Thomas). Please correct me if I am wrong, but it seems to me that this is where we're at. C. -- View this message in context: http://n2.nabble.com/problem-with-source-and-build-version-tp4106551p4131649.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
