Hi,
On 05/18/13 17:15, Sebastian Reitenbach wrote:
just install the gnustep-desktop meta package:
sudo pkg_add -i gnustep-desktop
then, I have this in my .xsession file in order to start windowmaker and
GWorkspace:
if [ -f /usr/local/share/GNUstep/Makefiles/GNUstep.sh ];then
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh
fi
export GNUSTEP_STRING_ENCODING=NSUTF8StringEncoding
export LC_ALL='en_EN.UTF-8'
export LC_CTYPE='en_US.UTF-8'
if [ -x /usr/local/bin/gpbs ];then
/usr/local/bin/gpbs
fi
if [ -x /usr/local/bin/gdnc ];then
/usr/local/bin/gdnc
fi
you do know that in theory, both these daemons get started
automatically? I have mysteiorus troubles on OpenBSD sometimes, but they
should start. Depending if you can run it as root or user, you can have
all GWorkspace daemons but also all gnustep daemons start automatically.
I would advice to start them before only on slow machines (< 400Mhz) or
if you use many gnustep apps. Read below.
You may have a slightly longer startup time, but what is the advantage?
On quite of the application they get automatically shut down again. So
if you just start one GS app occasionally, you won't consume memory and
resources!
wmaker &
if [ -x /usr/local/bin/GWorkspace ];then
/usr/local/bin/make_services
/usr/local/bin/GWorkspace
fi
You don't need to run make_services at every startup either. You need to
run it after every new application got installed.
So there are two ways: run it periodically like Apple does (well, but
they want you to buy a new MacBook every year) or run it after an
application install.
While this is not possible with a "drag&drop" install Apple-style, if
you install applications only through pkg, you could have a post-install
script run it perhaps?
Just suggestions of course, nothing wrong in your script, just different
optimizations depending on your usage style.
Riccardo
