Hi Derrell, thanks for your thoughts.
> Most Linux distributions either clear out /tmp each time the computer > boots, > or mount /tmp on a virtual file system (e.g. tmpfs) that is recreated on > each boot. I believe this means that on a laptop that is rebooted a few > times each day, an application in development would require a complete > rebuild following each boot -- a very long process, of course, with any > substantial application. Mh, I was not aware of that. I have been working with Linux the past 10 years and never had my /tmp been cleared automatically. But then, I'm not using one of those modern desktop versions of Linux. And actually, since 2 years I hardly reboot, I only hibernate. - But of course, I'm interested in other people's experiences. > I > would suggest using a different environment variable variable name, e.g. > QOOXDOO_CACHE_DIR, with a fallback to TMPDIR. I'm not sure I completely understand you here. For one thing, we are not evaluating environment variables. Technically, we use the gettempdir() function of one of Python's standard modules, tempfile. This in turn does evaluate environment variables, but also applies a lot of platform logic, so we don't have to worry about it. Since we are running But more importantly, the TMPDIR *is* the fallback already. Just set your CACHE macro to some other path and you're set. If you don't like the TMPDIR location, just override it. Config macros are our way of tailoring the system, and I wouldn't want to add another mechanism, like environment variables, without compelling need. - If you are running multiple applications on your machine, and want to maintain a central setting, just create some "site.json" and include it in the individual config.json's. But sure enough, while this should help you individually, the fallback setting should be sensible for most people, so if a lot of people have the issues you describe we should re-consider the default. > If QOOXDOO_CACHE_DIR is not > found in the environment, a warning should be issued (but not in -q > "quiet" > mode) because falling back to TMPDIR will cause the problem described > above > on each boot, causing a poor user experience of long build times. Maybe a > suggestion of how to add it to .profile could be provided. As I said, the solution is as close as your config.json. As for the poor user experience due to automatically erased /tmp directories, I would be interested to learn who else has this issue?! Thomas ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
