On 02/11/11 21:36, thron7 wrote: > Henrik, > >> Ahhhh, I see. Thanks! >> >> Now, I'm not sure, but that didn't quite come through from reading the >> docs. Maybe it's just me — maybe there's indeed a need for > clarification. > > Maybe the most important document to take in once you get into changing > the config is [1]. After giving a basic overview over Jason and how we use > it, the larger part of the document is a longish listing of the existing > config keys and their context (towards the end, "Listing of Keys in > Context"). As your error was related to context I wonder whether this was > apparent to you. Maybe, as there are only two contexts (top-level and > job-level), this fundamental information is not standing out enough, and > is overlooked. If you have any suggestions on how to improve on that I'm > interested to hear them. > > [1] http://manual.qooxdoo.org/current/pages/tool/generator_config.html
I arrived to the cache key documentation from the Google-found "Generator Configuration Articles" [1], particularly its cache key section, and a few pages lower, the section about the library key. It says the following: "The contribution source tree will then be downloaded from the repository, the generator will adjust to the local path, and the contribution is then used just like a local library. A consideration that comes into play here is where the files are placed locally. The default location is a subdirectory from your cache path named downloads. You can modify this through the downloads attribute of the cache key in your config." Then I clicked over to the reference and read the cache key's description (with its three supported subkeys). So I guess it might be useful to somehow hint in the documentation about how "cache" is not a root key. Which is I think the reverse of what "peer keys" currently define. That expression wasn't exactly clear until Tristan told me how to use the cache key. > >> And yeah, I want the cache itself totally outside my tree, which is why >> I specified a different place for the CACHE macro; but I just couldn't >> get cache/downloads to behave :) > > The "cache" key has two sub-keys, "compile" and "downloads". Tristan's > hint was right, but you want to change the "download" path, so this is the > sub-key you want to be using. If you set this in your config, the compile > cache should be in the default path, and the downloads in the path you > specify. > > The CACHE macro, on the other hand, only influences the path to the > compile cache, and the download cache is then a subdirectory of that, so > they both go together. If you want to separate the two, it is better to > set "cache/downloads" in your jobs. If you find yourself struggling with > getting the "cache" key working in the right jobs (source, ..., build), > you can alternatively try to use the (yet undocumented) CACHE_KEY, which > takes an entire map as you would assign to the "cache" config key. Again, > specifying the "downloads" sub-key should suffice > (tool/data/config/base.json holds a general sample of using this macro). > Yep, this part was clear from the first time I read "cache"'s reference. I think altering $CACHE and cache/downloads is enough. This makes sure anything depending on $CACHE will be affected consistently (particularly cache/compile itself), and will move downloads out from there as a special case, 1) to be web-accessible (this was one of my issues, can't reach stuff outside the document root with a web browser), and 2) so I have it nearby and don't have to travel across my file system to fetch the files (and have the option to version control them together with my own code). [1] <http://manual.qooxdoo.org/1.5/pages/tool/generator_config_articles.html> ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
