#JITSI VOIP CLIENT HOW TO#
#JITSI VOIP CLIENT INSTALL#
#JITSI VOIP CLIENT UPDATE#

#JITSI VOIP CLIENT INSTALL#

So while I am able to successfully install jitsi into my system, (in /usr/lib), using the ebuild, the /usr/bin/jitsi shell script produced by the ebuild needed several edits. > script as a template), and copying it to /usr/bin/jitsi, after the emerge. > is ugly, I ended up manually editing the file, (using the Archlinux jitsi

#JITSI VOIP CLIENT HOW TO#

> more modifications than I knew how to do in the ebuild. > included in the tarball, (resources/install/debian/jitsi.sh.tmpl), required > 2) The major issue is that the script template for loading jitsi that's > So… could you tell me how you got yours up an running at all? Because your I was basically pointing it out so that it was obvious it should be addressed somehow in the real ebuild. I've not seen that before, but I'm sure that experienced Gentoo devs have, and likely have a workaround solution for it.

#JITSI VOIP CLIENT UPDATE#

They seem to update their stable tarball releases in some manner similar to their nightly releases. What I was trying to point out by linking to it is that the jitsi folks don't seem to produce a real 2.0 stable tarball. The only stable, specific tarball that I could find, is the '2.0-latest' one. I don't think that's an optimal solution for a 'stable' package. xxxxx, then your ebuild will fail downloading the older tarball until the ebuild is updated, (or renamed). If the jitsi devs update their stable 2.0 tarball to version. The SRC_URI should link to a stable, specific one. > Also SRC_URI shoudln’t link to any “latest” version, but to a specific one. That way until it's in portage, we can have a current ebuild here. I'm hoping that someone who knows ebuilds can look at the ebuild and jitsi shell script, and determine the necessary edits to the ebuild to produce a clean, complete, emerge of jitsi 2.0. This is apparently a well known issue with various java implementations, so in order to get Jitsi to use my system font, I added the following hack to the jitsi shell script too Įxport _JAVA_OPTIONS='eSystemAAFontSettings=on' So, and I know this is ugly, I ended up manually editing the file, (using the Archlinux jitsi script as a template), and copying it to /usr/bin/jitsi, after the emerge.ģ) At this point I was able to get Jitsi up and running but the font it used was blocky and ugly. I don't know if the jitsi stable tarballs are updated regularly, but if they are, then this would mean that using the ebuild two different times could result in two different, albeit minor, versions being installed.Ģ) The major issue is that the script template for loading jitsi that's included in the tarball, (resources/install/debian/jitsi.sh.tmpl), required more modifications than I knew how to do in the ebuild. The ones I noticed are ġ) A minor issue is that it's downloading the 'latest' 2.0 source from the jitsi repository. However, there are several problems with it. So using Guillaume's ebuild from comment #14, I hacked up an ebuild I used to emerge jitsi 2.0 into my system. They even have an Android client in their nightly build section. It's not only open source instant messaging/voice calling/video chat, but there are OSX, Windows, as well as Linux clients available. I also really like Jitsi as well and think it would be an awesome alternative to Skype.

Jitsi shell script reference in comment #19

Jitsi voip client