MPlayer svn checkout
Hi Slack team!
Today i compile from SVN new version of MPlayer Code:
MPlayer 20110612-4.5.3 (C) 2000-2011 MPlayer Team This package based on Pat Slackbuild (little modified) |
Why would anyone else want this??
|
Quote:
|
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.
|
Quote:
|
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 :-)
|
Quote:
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.
|
Quote:
|
Quote:
|
Quote:
Code:
use_patents=${use_patents:-"no"} |
Point was that you should have. ;)
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 |
Quote:
# 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. |
I know how to read a SlackBuild script, and your quoting of the script, with the implication that I have not read it, offends me.
The line you quoted: Code:
USE_PATENTS=${USE_PATENTS:-"no"} Code:
USE_PATENT=yes ./MPlayer.SlackBuild I don't need anything to back this up, because it's true, but the README for Alien Bob's MPlayer package points out the exact same thing: http://slackware.org.uk/people/alien...MPlayer/README |
Hi @dugan. I think the real problem here is actually indicated in the OP's signature :
Sorry for bad English Russian Linux Beginner I don't think he meant any harm at all. |
All times are GMT -5. The time now is 11:02 PM. |