Hi,

I need a Skype package, in the style of the one made by Zerouno, with a mini-multilib included, but what I find use also whatever self-contained PulseAudio or APulse. However, right now the current tree is already Lennartized, then I suppose that there is no need for that part.

Someone know a Skype package adapted for the latest Slackware64 current?

Thanks!

I just read this today:

http://www.maximumpc.com/linux-commu...-skype-issues/

I've had Skype in my MLED repos for a while, but I've just had enough, and I'm definitely going to get rid of that junk, definitely. Everything Microsoft touches is either crap or evil, if not both. </rant>

Cheers,

Niki

While I agree that Skype is a piece of junk, that piece of junk is a must be, and a must be without Multilib, because is the only 32 bit program what I need, for even choosing between Slackware64 and the classic Slackware, on my brand new box which sports a Buldozer with 8 cores and 16GB memory.

I will install the 64 bit edition of Slackware version 14.2 when time will come, but then run Skype in a 32-bit VM. I use it infrequently so that should fulfill my needs.

1 members found this post helpful.

i've always just used the skype from slacky

1 members found this post helpful.

Thanks, but the current version from Slacky try to install a custom version of LennartAudio. I suppose that will conflict with the bare system...

Come on! I should go Virtual for one sick application?

Also, that box wait my decision, Slackware64 or Slackware32, to start kicking.

You can wait several months or years, looking to a virgin box which contains a several time better computer than your current one?

I didn't address your initial question, so sorry for this off topic answer. That being said, setting a VM is done in a matter of minutes. It happens that I need several ones anyway for testing purposes so it costs me nothing. But I admit that this is not your use case.

To counter that question, should you go with multilib or Slackware32 for one sick application? This isn't a sarcastic/rhetorical question. It really depends on your needs. If you really only have one application that needs 32bit, and you're not a fan of multilib, personally, I would go the VM route rather than limiting your whole OS and all the apps to 32bit.

But for me, I would just run multilib on the computers that have applications that require it. I have it on my main desktop for some games, but my htpc is pure 64bit.

The other option is to ditch skype and run something that is 64bit ready. I know this is probably easier said than done, but it might be worth considering. A few years ago when my then fiance I and were doing long distance, we tried several different video messengers, and hangouts worked great except it was pretty slow on her laptop (which is pretty ancient). We ended up with Skype just because it seemed to do better on lower resources. But Chrome has the largest share of users now, and hangouts works great if you have a decent computer from the last 5 or so years. I know Mozilla has their own thing (Hello, I think) that you could also look into.

Here is the one I got to work on my 64 bit Slackware Current system.

http://repository.slacky.eu/slackwar...kype/4.3.0.37/

1 members found this post helpful.

In many cases, Skype and the like is a corporate decision. But why is good, standardised SIP always overlooked?

Wow, that is such a good idea. I already have many qemu-kvm VM's for a variety of special tasks (mainly software building/testing on other ARCHes), I can't believe I never thought of running Skype in a 32bit VM. I just tried is and it works like a dream. Since my host has -current (therefore pulseaudio) installed, skype audio in the VM "just worked". The usb camera took a bit longer while I figured out the appropriate usb passthrough options but now it all runs great! Thanks for the idea Didier.

BTW I don't think this is overkill - the practice of launching a VM (or container) to make a single application available is pretty widespread. Also, from 'man lxc-execute': 'This command is mainly used when you want to quickly launch an application in an isolated environment'.

chris

Further to my other post praising Didier's idea to run Skype in a VM, it seems that this (a VM) is exactly what you want to run a 'sick application'. You clearly are concerned that you may catch some disease from it, so running it in an isolated environment will help to keep you safe and, at the same time, not force you to restrict yourself to a 32bit host system just to run Skype natively.

chris

Skype won't run in a virtual machine.

Edit: tried it a few years ago, but reading the post above makes me reconsider.

For running Skype in a VM I use the script which is attached below. You could use it as a starting point, changing the -drive and -cdrom entries to something appropriate (where -drive should point to the disk file created with qemu-img; and -cdrom should point to a Slackware installation iso). When the basic Slackware installation is done in the VM, wget the skype SlackBuild and its SOURCE tarball, build & install it. Nothing else to do really.

chris

Attached Files

VM_skype-14.2.txt (602 Bytes, 58 views)

1 members found this post helpful.