Re: Building full path before executing a GNOME binary.

[Hema Seetharamaiah <hema seetharamaiah wipro com>]

Havoc Pennington wrote:
> g_spawn doesn't search path by default, only if you specify
> G_SPAWN_SEARCH_PATH.  Most uses should probably not search the path
> and should just assume all of GNOME is in the same prefix.

G_SPAWN_SEARCH_PATH is enabled by default in g_spawn_command_line_sync
() & g_spawn_command_line_async ().

> IMO a complicated solution here is overengineering, we should just
> hardcode the paths when something is security-sensitive. GNOME is not
> realistically "piecemeal relocatable" (you can't install some of the
> desktop in one prefix and other bits of it in another).

I chatted with people on IRC on this and  what I gathered is that
security-sensitive instances need a case-by-case fix. 

For instance, one opinion was that gnome-control-center should be
ideally starting nautilus as a corba object and doing a
bonobo-activation rather than simply exec-ing the program.

Can the install path be got by using g_object_get_property() with
GNOME_PARAM_GNOME_DATADIR? Using the dir path returned, the full path
for a GNOME binary could be built? Or gnome_locate_file()?

Regards,
Hema.

**************************Disclaimer**************************************************    
 
 Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' 
and 'confidential' and intended for use only by the individual or entity to which it is 
addressed. You are notified that any use, copying or dissemination of the information 
contained in the E-MAIL in any manner whatsoever is strictly prohibited.

****************************************************************************************