Re: [Imservices-development] Firelite and Proteus 3

[Jason T. <tow...@ma...>]

OK, I believe I have the current state of everything checked in. I've  
cleaned out a lot of files from the firelite tree (which are now just  
used from the main Fire tree). There are still a few modified ones that  
over time I want to merge the changes in from, but for now they are  
still duplicated: ServiceController, MainController, etc.

To build Firelite you will need to check out three source trees and do  
two builds. Here are the steps:

How to build
------------

(You'll probably want to actually use SSH CVS instead of anonymous, but  
you get the idea.)

% cvs -d  
:pserver:ano...@cv...:/cvsroot/imservices  
login
% cvs -d  
:pserver:ano...@cv...:/cvsroot/imservices  
co imservices
% cvs -d :pserver:ano...@cv...:/cvsroot/fire login
% cvs -d :pserver:ano...@cv...:/cvsroot/fire co  
fire
% cvs -d :pserver:ano...@cv...:/cvsroot/fire co  
firelite
% cd imservices/imservices
% make all

Then build the Fire (Everything) target in Firelite.pbproj.

This is all in the Firelite-README.txt as well when you check out  
Firelite.

-Jason

On Thursday, July 3, 2003, at 11:33  PM, Jason Townsend wrote:
> With Justin's help this evening I was able to get Firelite launching  
> again, and editing accounts as well. It will quit when you try to  
> connect however.
>
> I hope to have these changes checked in this weekend and also update  
> the instructions on how you would build it and help out with getting  
> more stuff working.
>
> -Jason
>
> On Wednesday, July 2, 2003, at 11:06  PM, pr...@in...  
> wrote:
>> I'll post something about this when I get back into town, I'm out  
>> visiting
>> for a few days.
>>
>> You'll need to actually generate a key RSA512 bit, pass the public  
>> version
>> of that to the server, -then- connect (via authorize or addClient)
>> otherwise you'll just be refused access.
>>
>> Remote connections (not from localhost) have to be authorized,  
>> addClient
>> will just fail outright.
>>
>> There's a little bit of a different process, but I'll post it up, it's
>> nothing too complex.
>> - J
>>
>>> OK, I've run into a snag.
>>>
>>> I think I've got everything built correctly, but when I launch I  
>>> can't
>>> seem to connect to the imservices daemon. I can see it is running  
>>> from
>>> ps/top. I immediately get the daemonNotResponding error which says to
>>> try relaunching.
>>>
>>> I haven't checked any of this into CVS yet, but if anyone has ideas  
>>> on
>>> what I need to change in IMNotificationCenter let me know. I hope to  
>>> be
>>>  able to put this in CVS in the next few days.
>>>
>>> -Jason
>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>> Data Reports, E-commerce, Portals, and Forums are available now.
>> Download today and enter to win an XBOX or Visual Studio .NET.
>> http://aspnet.click-url.com/go/psa00100006ave/ 
>> direct;at.asp_061203_01/01
>> _______________________________________________
>> Imservices-development mailing list
>> Ims...@li...
>> https://lists.sourceforge.net/lists/listinfo/imservices-development
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/ 
> 01
> _______________________________________________
> Imservices-development mailing list
> Ims...@li...
> https://lists.sourceforge.net/lists/listinfo/imservices-development