MPlayer svn checkout
 

Hi Slack team!
Today i compile from SVN new version of MPlayer
If anyone would testing this, try my package http://slackfire.info/pub/Linux/pack...612-i486-1.txz
This package based on Pat Slackbuild (little modified)

Why would anyone else want this??

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.

Sure, http://slackfire.info/pub/Linux/pack...yer.SlackBuild thats my Slackbuild, everyone make use it, because its in slackware tree (but i modified only version and delete one configure option)

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.

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)

You didn't take the opportunity to build it with USE_PATENTS set to YES?

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:

# 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.

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:

means to use "no" for the value of USE_PATENTS only if it's not already set. In other words, launching the SlackBuild with the line that I gave you:

would set the value of that variable to YES, within the 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.

Im understand you, really. I dont understand difference between this line in in Slackbuild and if i run Slackbuild with USE_PATENTS=no.

@anti-user - due to the most ridiculous patent system in the world, the US Government has allowed companies to patent software methods. In this particular case, it means that MPlayer is not allowed to use certain libraries because patents are held on them. The 'not-allowed' means that nobody may distribute compiled programs with these methods in them. But you can download the source code and compile it yourself. Now - if you build with 'patents=No' you get a MPlayer binary that can't play certain files. But if you compile with 'patents=Yes' then you get the full library of codecs, including the ones that are patented (like mp3/h264 etc). Stupid heh ! Luckily you and I live in countries that don't have that nonsense. Yet.

yes... and what will be legally to distribute Mplayer - to compile with patents=No? but if i want to have fully working MPlayer and dont distribute this (using only mine) i should compile this with patents=YES flag?
If so, i would like to distribute this and compile with patents=NO flag.

That depends (I think) on exactly where you distribute from. If from the UK (like AlienBob does), or from your country (Russia), or from my country (South Africa), then you are fine and you can build and distribute with patents=Yes. Of course, whether citizens in the US are allowed to download those binaries may be a different issue - I'm not sure about that. Either way, as I said before, your efforts are best appreciated when you show us exactly how you did it and what you changed to make it work. Not that MPlayer is all that hard to build anyway - compared to the effort that AlienBob has put into his vlc slackbuild. Now there's a work of art !

Great, im very pleased to Patrick, that he made this Slackbuild with much options...