Hi, ok, I guess if we can make sure that the user normally doesn't have to set anything and we don't have to change any system settings we should be ok. Remember that we do want to still provide a single directory install (zip file) where the user can run blender without needing to set up anything.
As for the rest of your suggestions, I've put my thoughts beneath your suggestions - I think we're mostly on the same page, just some details vary ;) Let me know what you think, Andrea GSR schrieb: > Hi, > and...@aweikert.de (2010-03-30 at 1920.16 +0200): > >> For the multi-user installation, there is a start of a description in >> the wiki where the paths that blender uses are set via environment >> variables, which I don't really like since they are cumbersome on >> Windows to setup. They are also likely to be forgotten to set by users >> or point to wrong versions of Blender etc. which will lead to bug >> reports and at least some maintenance work for the devs. >> > > The env vars are, first, a method to pass the info to children > processes (and to receive from parent if Blender is being launched > from scripts), and second a configuration system. > > The default initialization is from a file and some internal code (to > handle versions, etc) so only very advanced users should need to > change things by hand, the rest should be fine with defaults or a file > rewritten by Blender. > > GSR > > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers