trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] Is anybody able to start the groupwise wizard in R14?

From: "David C. Rankin" <drankinatty@...>
Date: Thu, 13 Feb 2014 22:59:17 -0600
On 02/13/2014 10:38 PM, Darrell Anderson wrote:
>>> I notice in your screen grab you do not have a button for Novell 
>>
>>> Groupwise. 3.5.10 has that button:
>>>
>>> http://humanreadable.nfshost.com/misc/groupwise-3.5.10.png
>>>
>>
>> What got deleted? I haven't seen that in any of my new builds???
> 
> I traced the disappearance to commit cc29364f, 2010-09-01.
> 
> Probably made sense some time ago when Novell owned Suse and Novell 
> Groupware and SLOX were much one and the same. I don't know whether 
> Novell Groupwise is valid anymore or whether that option should be 
> restored.
> 
> There also is code for Microsoft Exchange but the button is 
> deliberately hidden. I filed an enhancement request.
> 

You requested that code should be deleted right?

> I don't use the app. I was just testing.
> 

If you don't use eGroupWare -- I suggest you, and everyone else on the list, go
download it:

svn checkout http://svn.egroupware.org/egroupware/branches/1.8/aliases/default .

take the 10 minutes it takes to setup, and forever more have a complete
open-source, mysql backend, M$ exchange replacement. (really, it holds all your
contacts, calendar, knowledge base, time sheets, projects, etc...) in mysql
tables that will stay with you from now on. It provides seamless integration
with TDE and you smart-phone/tablet as well via caldav/cardav/groupdav or
xmlrpm. Enter a calendar event on your phone in Alaska, and it pops up on your
TDE desktop in Florida, and then reminds you of the appointment with
dual-configurable alarms, it's slick :)

>> Are you sure you don't have some global patch that is getting 
>> applied somewhere
>> in the bowels of you build scripts? Even then, I can't see how 
>> that would cause
>> the linking to fail without it blowing up your build. That is the 
>> strange part.
> 
> The solution turned out to be adding /opt/trinity/lib/trinity to 
> /etc/ld.so.conf. I always have had /opt/trinity/lib, but never 
> /opt/trinity/lib/trinity and never needed that either. I don't know 
> what changed the past weeks or months that requires that now.
> 
> Darrell
> 

Hah! It was something simple - glad you solve the issue.

-- 
David C. Rankin, J.D.,P.E.