Raysession document dependencies ?

[newlaurent62]

Hello,

For some clients, i need to override the XDG_CONFIG_HOME variable to $raysession_path/etc/$NSM_CLIENT_ID/, I did not find a way to do it with client proxy model so i created a wrapper script that launch the real client with the XDG_CONFIG_HOME exported. Each client has therefore a set of configuration files. Configuration can be modified for each client without changing the user configuration in ~/.config. And as the configuration files are stored in $raysession_path, The RaySession document is portable.

Is there a property that define the executables (wrapper script and real program) needed to start:

• a client
• a session

ray_control could check whether the required programs are available in the system before starting a client or a session. This check could be optional.

ray_control client set_properties dependencies:"program1,program2 ..." ray_control client get_properties dependencies ray_control client dep_check return 0 if success all program have been found and 1 if a program coul not be found. Prints every program missing on stderr to be able to popup a message to the end user.

ray_control set_properties dependencies:"program1, program2 ..." ray_control get_properties dependencies ray_control client dep_check return 0 if success all program have been found and 1 if a program coul not be found. Prints every program missing on stderr to be able to popup a message to the end user.

BR, Laurent

[newlaurent62]

ray_control could also define:

ray_control enable dep_check ray_control disable dep_check

[Houston4444]

Hi ! Are you really sure to need to connect some files to outside of your proxy dir ? I said this because it breaks the client portability. If you do that, if user saves this client as template, this template won't works ! If the config files are not too large, I suggest to copy all the config files to all proxy dir. Please use proxies and clearly not direct client when they use config files inside session dir. I don't see why a wrapper script in proxy could not work.

The only existing dependency check is for factory client template. the XML attribute 'try-exec' contains all needed executables separated by a semicolon ';' . It would be possible to add this to user client templates. I don't really like the idea to add this to session, but you can easily prevent session open with dependency check with session scripts.

[newlaurent62]

Indeed i don't need to connect outside, i will put the configuration directories in the client proxy dir.

I will test my wrapper under ray-proxy client.

Thanks for your help.