http://bugzilla.moblin.org/show_bug.cgi?id=10477
--- Comment #2 from yongsheng zhu <[email protected]> 2010-04-14 21:37:22 PST --- > My proposal for a short-term solution: > - build a white list of "known" env variables (grep the source code) > - extend D-Bus API to transfer those > - set them temporarily when running the operation, remove again > afterwards (can be done via list< boost::ptr<ScopedEnvChange> >) do we need to include env variables used for client-test? currently they are not used in command line, but I wonder whether we consider them. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
