Using gmail to call landlines and mobile devices (make google package with src2pkg)

hitest · 08-31-2010, 09:33 AM

Last week google introduced the capability of using gmail to call other people in Canada or the US on landlines or mobile devices. This capability is free for 2010.
I gave this a try in Slackware 13.1 and it works.

To do this I was browsing with Fire Fox 3.6.8 and logged into my gmail account. On the left hand side of your e-mail account window you will see a phone icon.
1. When you click on that icon you will be prompted to install the gmail phone application.
2. A download window will open asking you to download a .deb source. I downloaded it and then I used src2pkg to create a Slackware package, then installed it.
3. Re-launch Fire Fox.
4. Click on the phone application and call up people. The voice quality is quite good, I experienced little lag.

Edit: added later. Thanks to bgeddy for pointing out that this method works for 32 bit Slackware.

mlangdn · 08-31-2010, 11:05 AM

Are you running 32 bit Slackware? It did not work on my Slackware64-current. Although the downloaded file was for 64 bit, when I click on the Call Phone, it wants me to download the voice plugin. I already did that and installed with src2pkg.

hitest · 08-31-2010, 11:10 AM

Quote:

Originally Posted by mlangdn

Are you running 32 bit Slackware? It did not work on my Slackware64-current. Although the downloaded file was for 64 bit, when I click on the Call Phone, it wants me to download the voice plugin. I already did that and installed with src2pkg.

Ah...I should have mentioned that, my bad, mlangdn. I'm running 32 bit Slackware 13.1.

bgeddy · 08-31-2010, 11:40 AM

Quote:

Are you running 32 bit Slackware? It did not work on my Slackware64-current. Although the downloaded file was for 64 bit, when I click on the Call Phone, it wants me to download the voice plugin. I already did that and installed with src2pkg.

The GoogleTalk plugin won't work on pure 64bit systems as we discussed here. This is a real shame and actually gives me a real reason to possibly persue mutlilib. I have not wanted to so far preferring to stick with a pure 64 bit as I feel there's less to go wrong with that set up. Still thinking abut it

Lufbery · 08-31-2010, 01:44 PM

Bgeddy,

I resisted a multi-lib setup with Slackware 13, but decided to go multi-lib with Slackware 13.1. Everything has gone very well. The biggest thing I gain is Wine, running 32-bit Windows programs.

One tip, grab Eric's packages for multi-lib and Wine (if you want that) to make things a lot easier.

After I installed the mutli-lib files according to Eric's the instructions, I had to make compat32 versions of a couple of updates that happened after Slackware 13.1 was released: seamonkey-solibs, libtiff, and libpng.

I use the Nvidia driver Slackbuilds.org package, so I also made a compat32 version of that package.

Regards,

bgeddy · 08-31-2010, 02:59 PM

Quote:

I resisted a multi-lib setup with Slackware 13, but decided to go multi-lib with Slackware 13.1. Everything has gone very well. The biggest thing I gain is Wine, running 32-bit Windows programs

Yes - I admit Wine was a real draw for me as well as Skype (don't know if there is a 64bit Skype yet but there wasn't). I seem to remember seeing talk of Adobe dropping 64bit flash as well - my current version works fine though and think this may be a temporary hold up as they update their code base.

Thanks for the tips - I am still thinking about this but will be checking into exactly what is involved. I once built a CLFS system so I have a fair idea of the implications but that was a long time ago and memory fails somewhat. In any case , thankfully Eric has done all the hard work anyway so it shouldn't be too difficult.

Anyway, apologies to hitest for perhaps derailing his thread a bit.

hitest · 08-31-2010, 03:24 PM

Quote:

Originally Posted by bgeddy

Anyway, apologies to hitest for perhaps derailing his thread a bit.

No need to apologize. I'm not running 64 bit Slackware at the moment so I was unaware of the issues you brought up.
Thank you for discussing that, bgeddy. I've edited my first post to indicate that what I did was on 32 bit Slackware.

mlangdn · 09-01-2010, 09:08 AM

I downloaded Alien's multilib packages last night. Once upon a time, I was multilib. I'm sitting here wondering if the plunge is worth it again. I'm gonna have to first recompile the kernel for 32 bit support. That won't take long, but I'm just lazy.

njb · 09-01-2010, 10:23 AM

Quote:

Last week google introduced the capability of using gmail to call other people in Canada or the US on landlines or mobile devices

Apparently this is valid only in US and Canada

NjB

njb · 09-01-2010, 11:10 AM

I have slackware current
What can I do with
Alien's multilib packages
Am I missing something ?

NjB

mlangdn · 09-01-2010, 11:26 AM

Alien's multilib packages enable one to run and/or compile 32 bit software on a 64 bit system. Is your -current 32 bit or 64 bit?

njb · 09-01-2010, 12:47 PM

Quote:

Is your -current 32 bit or 64 bit?

My current is a 32 Bit.
In the near future, as I am satisfied with my slackware experience, I expect to install it in a 64 Bits machine.
I've found a very thin PC wich seems good to me.
ACER Veriton L670G
The one with the core 2 duo
I think core 2 duo is 64 Bits.

But then I need to know if I can get all the applications that I need in the 64 Bit version.
That's the question !!

;-/ NjB /

mlangdn · 09-01-2010, 03:23 PM

Generally, but not always (wine comes to mind here), compiling source code is not a problem on 64 bit, assuming you meet any dependencies first. It just requires a bit of research. If the application you need is available only in a 32 bit binary form, you will need multilib.

I'm still fiercely fighting off going multilib, hoping that for some things (google earth is but one), a 64 bit binary will become available soon.