Yate server > Installation from packets/SVN/.exe/AppStore

Ubuntu Packages

(1/4) > >>

vankooch:
Hi,

I'm building Yate debs for Ubuntu for a some time and now I want to setup a new PPA on lauchpad. As Yate has a lot of modules and it can be used for a wide range of usecases, I've split them in different groups/debs. The problem is that I just use some limited working scenario. To have a correct grouping I could need some help.

Current Debs:

* Yate: binary,shared,man
* libyate: lib file
* Yate-dev: yate-config, includes
* Yate-doc: docs
* Yate-client: Client files (gtk,..)
* Yate-scrips: sample scripts
* Yate-pgsql: Postgree Driver
* Yate-mysql: Mysql Driver
* Yate-openh323: OpenH323 Chan
* Yate-javascript: Javascript module
* Yate-gvoice: Google Voice module
* Yate-jabber: Jabber modules
* Yate-signaling: ysigchan, mgcpca, mgcpgw, ciscosm, sigtransport, lksctp, isupmangler 
* Yate-monitoring: cpuload, monitoring, ysnmp
* Yate-core: Rest of modules
This is only a starting point so if you have any ideas you are welcome!

Update:
You can finde the ppa under:
https://launchpad.net/~sico/+archive/yate

Diana Cionoiu:
I don't see a reason why  Yate-javascript: Javascript module, Yate-gvoice: Google Voice module, Yate-jabber: Jabber modules will be apart from the yate core.

If you have too many packets than is hard for a user to figure out what is going on.

asymetrixs:
I think it is good to split it up. As long as all core-packages are packed together so that yate can startup with minimal modules it is ok. So people can decide which modules they want to use and which they do not use. This is for example the same as apache is doing it. You can download apache and as module php support. So in my opinion it is the right way to do it, because it leaves it up to the user to install what he needs.

Diana Cionoiu:
I disagree because in the case of apache and php, the php module of apache requires an installation of php, while the jabber module of Yate doesn't require something external, except ssl, which exists on every single system I know.
And javascript module doesn't even require ssl.

asymetrixs:
Yate is developed in a modular way. It is up the the user to choose what he wants to compile and install and what he does not want to use. When the sources offer the flexibility of choosing which modules should be build, then also any package should provide this flexibility. Otherwise users could think that they do need to compile yate on their own if they only need specific modules and therefore they would not use the provided packages. Moreover if you have only one packages, one might wonder about its content. You could call it "yate with all modules" but "all" is not defined properly. It could mean that all modules of yate team are build in, but what about custom modules? Providing packages for each module also gives everyone else, who uses (self developed) modules, the opportunity of providing their module as package. Then - if they want to give it to the public - they only need to provide the module it as package, publish it and it should work. If all modules were in the same yate package, it would be impossible for someone to add a module to the package without contacting the package maintainer. And then it would be the work of the package maintainer to rebuild the package and to make it work "somehow", because people would expect it to work. So if it does not work when it is provided in a modular way,  the package provider - who published the module - can check what the error is and fix it. Then there is no need for the maintainer to deal with a problem of a module he does not know. Providing package modularity gives the author of a module the flexibility of providing the module package and only to maintain this package.

Yate is developed in a modular way. Compiling yate from sources give the user the flexibility of choosing the modules to compile and to use. Keep the modularity up, in any way.

Navigation

[0] Message Index

[#] Next page