On 10/20/06, Quentin Mathé <[EMAIL PROTECTED]> wrote:
Le 20 oct. 06 à 20:32, Yen-Ju Chen a écrit :
[snip]
> I did something like that to start Azalea through gnome-session > some time ago. I would be curious to know how. ?
Here is my /usr/share/xsessions/azalea.desktkop: [Desktop Entry] Encoding=UTF-8 Name=Azalea Comment=Use this session to log in Etoile Exec=/usr/local/bin/start_azalea Icon= Type=Application And /usr/local/bin/start_azalea (chmod 755): #!/bin/sh source /usr/local/GNUstep/System/Library/Makefiles/GNUstep.sh openapp AZDock.app & sleep 1 openapp Azalea.app I also source GNUstep.sh in my .bashrc.
> The other issue I have is the possibility to start etoile_system > without menu server. This won't be an issue once every processes to manage will be specified by a config file (the code is already written but not yet in use). > In another word, does etoile_system is as flexible as a script for > startup Etoile system ? A lot more since its shares many similarities with something like launchd, but extended with session management related features.
I am not against etoile_system since it has other functions. I just think a script like start_azalea above may reduce some problem of having tools and libraries outside GNUstep directories. Yen-Ju
> If not, maybe a script to start everything is a better solution. > But it is not that important for now, I would say. The main problem at this time is the need to have libgnustep-base.so and libgnustep-gui.so linked in /usr/lib. This is specially problematic when you develop on Debian/Ubuntu system which are already linking these GNUstep libraries too when GNUstep is installed. It's important to know that in .desktop file for GDM you cannot specify something like 'opentool etoile_system', the first process executed is the process which represents the session. In this case, the owner is 'opentool' which exits immediately. Everything gets harder at this point. But anyway our problem could be solved by linking statically libgnustep-base.so (in the case we avoid to link AppKit) or by parsing GNUstep.conf, but this last option might fail, so I would be in favor of the first option. Otherwise I think we cannot avoid to link openapp/opentool in /usr/ local/bin or at least a place where we are sure we will always be able to find them. opentool/openapp allows to launch programs without sourcing GNUstep.sh, then they are used by etoile_system to launch any processes. It's a pity we cannot use them for etoile_system itself. This would eliminate any library search path issues. Cheers, Quentin. -- Quentin Mathé [EMAIL PROTECTED] _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
_______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
