[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: problem porting sogo to use gnustep-make 2

From: Nicola Pero
Subject: RE: problem porting sogo to use gnustep-make 2
Date: Thu, 10 Jan 2008 22:33:44 +0100 (CET)

Well, it really depends on how sogo is installing resources/files at 
install-time and 
then finding them at run-time. :-)

You first need to figure that bit out - ie, look around at the source code, 
where the resources are installed and then looked up.

If it has its own internal 'sogo-specific' mechanism, then well you need to
debug that mechanism ;-) - it might not have much to do with gnustep.  You are 
forcing installation in some paths of your choice, and then you need to make 
that at runtime Sogo can find things where you installed them. ;-)

If it's using the "standard" GNUstep resource location system (which I'd 
recommend), then you need to make sure that everything goes through the
standard GNUstep APIs, with no exceptions:

 1. at install time (in GNUmakefiles), specify all installation locations using 
the gnustep-make v2 variables and terminology (eg, GNUSTEP_LIBRARIES, 
GNUSTEP_TOOLS, etc. PS: Note that we also have GNUSTEP_WEB_APPS that was 
introduced precisely for OGO/GNUstepWeb).  This might mean that on one machine 
in practice gnustep-make will install things into /usr/lib/sogo while on 
another you install into /usr/GNUstep/System/Library/Libraries/sogo or 
something else, depending on how GNUstep was configured on that system, but 
don't worry because it will all be found at
run time if the right API is used.

 2. at run time, use the standard OpenStep/gnustep-base API (NSPathUtilities 
and such) for locating resources; each gnustep-make variable has a 
corresponding variable in that API to find the resources.  gnustep-base will 
automatically map that to the local filesystem and find it.

In this case (GNUstep API), you should look for inconsistencies, eg, resources 
installed in hardcoded paths but being looked up using the OpenStep API, or 
vice versa
resources being installed using the gnustep-make API but then being looked up
using sogo-specific code that follows a different logic ;-)


-----Original Message-----
From: Sebastian Reitenbach <address@hidden>
Sent: Thursday, January 10, 2008 5:46pm
To: address@hidden
Subject: problem porting sogo to use gnustep-make 2


to install sogo, there still was gnustep-make 1.13 used. 
I changed the makefiles to install the libs in /usr/local/lib, bundles 
below /usr/local/lib/sogo-0.9 and the web templates/webserverresources 
below /usr/local/share/sogo-0.9.

On OpenBSD, using the gnustep-make port, sogo finds the templates, 
webserverresources, ... I got it to start up, and even authenticate me ;)

Then I switched to openSUSE 10.3, I used the gnustep-base and make rpm's 
from here: http://www.cenon.info/frame_gb.html.
On Opensuse all files end up in the same place as on OpenBSD. 
Then sogod starts up, I also see a line in the output:
[SOGoProductLoader]> scanning SOGo products in: /usr/lib/sogod-0.9
so these seems to be found.
but when I try to access the page that sogo should provide via a browser, I 
get error messages about not found objects.
I straced the sogod when I tried to access it with the browser. 
I saw it searching for bundle-info.plist files for e.g. MainUI.SOGo 
(MainUI.SOGo is in /usr/local/lib/sogo-0.9) but there is no such file in 
that directory. There is also no such file in that direcotory on OpenBSD, so 
I am not sure whether this is my actual problem.

On OpenBSD the GNUstep filesystem layout is nearly FHS like, so all stuff 
goes into /usr/local/{bin|sbin|lib|share}
With the rpms for OpenSUSE, all the GNUstep stuff goes into /usr/GNUstep.

I assume that I do not have a problem to run sogo on OpenBSD because the 
GNUstep filesystem layout fits well there, but as it is completely different 
on the Linux box, some lookup paths are pointing to where the actual 
bundles... are.

Hopefully someone understood what I wanted to say and maybe has an idea why 
it works with GNUstep on OpenBSD but not on openSUSE.

Any hint on debugging or providing further information would be a great 

kind regards

Discuss-gnustep mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]