SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Pat package is half year old, mplayer is already strongly updated, thats why i publish my package. I change only two lines of Pat slackbuild - its version (update to 20110612) and obsolete configure option --enable-largefiles (delete this)
I think what we're really interested in is how you did it. Perhaps post your SlackBuild script. We don't want to shoot you down, but the vast majority of people here don't like running binaries (ie compiled programs) when they can't be certain of the origin (ie where it cam from). To put it in plain English - how do we know that you don't have a virus or trojan code in the program ? But show us how you build it and we can do the same. No offense intended.
I think what we're really interested in is how you did it. Perhaps post your SlackBuild script. We don't want to shoot you down, but the vast majority of people here don't like running binaries (ie compiled programs) when they can't be certain of the origin (ie where it cam from). To put it in plain English - how do we know that you don't have a virus or trojan code in the program ? But show us how you build it and we can do the same. No offense intended.
Ah - but your original post never mentioned that it was slight modification of Pat's SlackBuild. All you offered was a compiled binary. Like I said, I'm trying to show you the etiquette of dealing with this forum. Your efforts are welcomed. Your compiled binaries are not. Remember, we use Slackware because it's Open Source. If we wanted binaries, we'd use Windows. Cheers :-)
Ah - but your original post never mentioned that it was slight modification of Pat's SlackBuild. All you offered was a compiled binary. Like I said, I'm trying to show you the etiquette of dealing with this forum. Your efforts are welcomed. Your compiled binaries are not. Remember, we use Slackware because it's Open Source. If we wanted binaries, we'd use Windows. Cheers :-)
i dont force anyone to use it, use it if you would, if nor - dont use it.
source code of this version located on this site of my host
OK - @anti-user, I can see we have a language issue here. Let me start at the beginning and explain this clearly. Thank you for your showing us that MPlayer can be compiled from the latest checkout. Those of us who use MPlayer (and love it) are pleased. In your excitement to show us this build, you may have forgotten that Linux people (and especially slackware people) are suspicious of programs where that can't be certain of the origin. In all fairness, you are not one of the people who have built up a trust over the years (Like Pat, AlienBob, RWorkman etc). Those people we trust and we'll download binary code from them easily. I'm not saying you're a crook or a cracker or a spammer or anything like that - but how do I know you're not ? The answer is that I don't - and that's why I can't trust you until you've built up plenty of credit here. And that takes a long time. The internet is a nasty place - lots of bad people floating around. So, by all means, tell us that the latest MPlayer works, show us how you did it (version downloaded, slack mods, any compile issues, will it work on 64-bit ?). We'll happily look at your scripts. But no-one here will download and run your binaries. Yet. Thanks.
OK - @anti-user, I can see we have a language issue here. Let me start at the beginning and explain this clearly. Thank you for your showing us that MPlayer can be compiled from the latest checkout. Those of us who use MPlayer (and love it) are pleased. In your excitement to show us this build, you may have forgotten that Linux people (and especially slackware people) are suspicious of programs where that can't be certain of the origin. In all fairness, you are not one of the people who have built up a trust over the years (Like Pat, AlienBob, RWorkman etc). Those people we trust and we'll download binary code from them easily. I'm not saying you're a crook or a cracker or a spammer or anything like that - but how do I know you're not ? The answer is that I don't - and that's why I can't trust you until you've built up plenty of credit here. And that takes a long time. The internet is a nasty place - lots of bad people floating around. So, by all means, tell us that the latest MPlayer works, show us how you did it (version downloaded, slack mods, any compile issues, will it work on 64-bit ?). We'll happily look at your scripts. But no-one here will download and run your binaries. Yet. Thanks.
Okay, this version tested on x86 platform, this is i486 package. Im run this modified Slackbuild and take ready to use package. Of course anyone may upload package with trojan, virus (often is openssh/openssl hack)
Also, that line of the SlackBuild didn't have to stop you. You could have launched the SlackBuild with:
Code:
USE_PATENT=yes ./MPlayer.SlackBuild
# The Slackware package is built with "USE_PATENTS=NO" i.e. without using
# the lame mp3, faac, AMR and dvdcss libraries.
# This also means that this creates a version of MPlayer that is unable
# to play encrypted DVD's (which is most DVD's on the market). If it is
# allowed in your country to use libdvdcss, this is not a big problem though.
# Install a libdvdcss package and it will be picked up automatically by
# MPlayer's internal libdvdread library, so that MPlayer will again be able
# to play encrypted DVD's.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.