request for packaging

[Diana Cionoiu]

Hello Kilian,

I will like to start by saying thank you for your work.
I'm sorry for the "Dokumentazione" part, our site is a wiki and someone 
has put some graffiti since it was Christmas, we haven't done so fast the 
roll back.
YateGUI is another package and another story, the new version will be 
available until 15 january, so the one that we have dosen't worth the 
trouble. The new one we don't know if is working with Kaffe since is using 
swing. I recomand to not do a package for it.

The ldconfig problem has been solved in the cvs version (who will become 
very soon 0.8.6 - the last version from branch 0.8, we hope to have 0.9 
branch in january).

On my sistem where i have installed zaptel from sources using "make 
install" the zaptel.h is in /usr/include/linux/zaptel.h . I don't know 
debian packages but normaly it should be a zaptel-devel package.

The reason for libyate.so to be in /usr/lib is because that is a more or 
less a generic library and it can be used in other projects, in fact we 
started a new project now that is using that library. The other reason is 
that /usr/lib is in the library path so if you wanna be able to start yate 
you must have libyate in the library path (/var/lib/yate has no reason to 
be in the library path, the .yate files from there are loaded by 
libyate.so).

The test directory has some modules used to test the main yate engine.

I think i should clarify some things regarding yate. Yate mean Yet Another 
Telephony Engine. Is made by a few parts.

1. The generic library - contain classes like String, Thread, Message and 
so on. (the header is telengine.h). We've made our own library to have the 
Message base system.
2. The telephony library - contain classes like DataSource, DataConsumer 
and so on (used to pass telephony related data, the header is telephony.h)
3. The modules - each module is standalone (modules are communicating 
between them by using messages with variabile parameters).
4. Libraries - in the contrib directory we have put some libs used by 
modules ( qt by qtclient, iax - for iax module, sip - for the sip module).
5. The test suit - is in the test directory.

Yate is not asterisk, it runs like apache. You start yate with -d as a 
demon or you get the messages on the screen. To control yate or to do 
other things you can do a "telnet 127.0.0.1 5038" and try the help 
command. So normaly you should have a script like for apache (in mandrake 
is in /etc/init.d ) to start and stop yate. 

I also think that libyate should not be in a different package.

Diana

> Hi again,
> 
> i just wanted to add the remarks i have about the package so far:
> 
> - the GUI isn't packaged. I'm not sure from the "Dokumentazione" if
> that's possible or even intended from the main package. Yet as it's
> Java, i'm not even sure how this shall be achieved as there's only the
> free JDKs like Kaffee in Debian.
> - i had to remove ldconfig calls from the Makefiles to ensure the
> package can be built as user
> - the zaptel.h is only available in zaptel-source. I somewhat hacked the
> include to /usr/src/modules/zaptel/zaptel.h .. not sure if that's a
> "good" solution, but it kinda works
> - so far i'm very unhappy with /usr/lib/yate/ for the modules. I'd
> rather have this within /var/lib/yate/, but can't find a switch to make
> this be relocated in configure
> - from the docs i read that there's a make test. I'd love to include a
> validity test to ensure the built package works as intended (has proven
> a great help with openh323 apps *g*). Is it safe to be included into
> building? What will it test? Does it require root? There's not very much
> verbose output to what is actually being tested and what's the result.
> Plus multiple executions of ./mktestlinks yield:
> ln: `randcall.yate': File exists
> ln: `msgsniff.yate': File exists
> 
> - the Debian package is *VERY* beta.. I have just tried to make it
> compile and execute cleanly. So far i can start the yate, but i don't
> receive a "console" like in asterisk.. rather it just hangs in mid-air
> not telling me if it was done now or waiting for something.
> 
> 
> For all the voip DDs, i have commited yate/trunk to pkg-voip SVN for
> everyone to toy around with it. Don't tell me it cannot be uploaded like
> this, that wasn't my intention. I'd rather like to know if the packaging
> (i.e. the control and rules) are ok like this. Once this is settled,
> i'll finish the README and stuff so we can pump this onto the ftps..
> 
>