Richard van Paasen said the following, on 12/02/2008 18:42: > Hi, > > I finally got it working by pointing some environment variables to different > locations (it's a bit ugly, but I couldn't get it to work otherwise): > > export OS_CACHEDIR=$HOME/tmp/os-cache > export FREEVO_CACHEDIR=$HOME/tmp/freevo-cache > > export OS_STATICDIR=$HOME/tmp/os-static > export FREEVO_STATICDIR=$HOME/tmp/freevo-static > > I have different users for freevo development and freevo production version > and they don't have write access to each other's files. >
Interesting that you have different users. What Freevo does is to use the current directory first, then ~/.freevo and finally /etc/freevo and /var/<dir>/freevo where dir is log, lib, cache. This means that so long as ~/.freevo exists for each user then your local_conf.py, cache, static (lib) and log files should be separate for each user and so each version. This should make it easier and cleaner. > The freevo production version is the 1.7.4 release that comes with Gentoo > portage. It is installed system wide and so is kaa for that version. For the > freevo development version, I installed kaa in ~/lib/pythonx.x/site-packages/ > and for freevo I created a link in site-packages to the svn version of freevo. > In this case PYTHONPATH is your friend, actually you can run freevo with the options -d -d (debug) and it should write a small gdb script in /tmp. Basically the freevo script is just a set-up program that sets the environment variables before calling main.py, so it should be possible to set the environment variables and then run python main.py. HTH Duncan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel