Le 20 oct. 06 à 20:32, Yen-Ju Chen a écrit :
On 10/19/06, Yen-Ju Chen <[EMAIL PROTECTED]> wrote:
On 10/19/06, Quentin Mathé <[EMAIL PROTECTED]> wrote:
> Author: qmathe
> Date: Thu Oct 19 16:39:59 2006
> New Revision: 1040
>
> URL: http://svn.gna.org/viewcvs/etoile?rev=1040&view=rev
> Log:
> Major update to introduce basic session management and better
process
> handling in System (based on code written by Saso Kiselkov). Log
out will be
> supported once MenuServer is updated.
Currently, setup.sh install some tools and libraries into
/usr/local/lib and /usr/local/bin
in order to start etoile_system without source the GNUstep.sh.
Wouldn't it be easier to have a script called start_etoile.sh:
#!/bin/sh
source /usr/local/GNUstep/System/Library/Makefiles/GNUstep.sh
etoile_system
We can have this script installed in /usr/local/bin
and have etoile.desktop execute this script.
This was my initial plan, but it doesn't work with GDM, probably not
with KDM etc. either. I remember to have posted an explanation on
this issue recently.
In this case, we don't need setup.sh and setupdown.sh anymore.
I don't think so, because setup.sh/setdown.sh handle many other
unrelated things.
I did something like that to start Azalea through gnome-session
some time ago.
I would be curious to know how. ?
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.
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
