SMPlayer Support Forum

Thanks RVM & redxii. But I am a little confused.

You just made a change yesterday in svn 4379 - which wasn't even posted. And today redxii has 4380 pkgs already posted?!?

Are the svn versions chronologically sequential? (for most software, they are) It must be relatively quick to take minor changes (like the "mplayer.exe in lower case" - in svn 4379) & sort of automatically generate a new Windows packages (4380), ready for d/l, in < 1 day. I'm appreciative, just not sure how it happens that fast.

I built a new MPlayer too, it only takes about 10 minutes for me to compile everything.

Thanks for clarification. When you build a new SMPlayer / MPlayer, generally - are you taking the most recent svn version from rvm? I assume so (that can bite you), as his latest, yesterday was 4379 & the Windows ("unstable") you posted today is 4380.

I'm just clarifying that all the most recent changes (like the ones rvm kindly obliged me on, recently) get into your builds - IF your version(s) is = or > than rvm's most recent svn #. A coder would know the answer (which I'm not), but I test a lot of software.

They are the same code. I updated my copy to r4379, then made a commit which brought up the revision to 4380. It only takes seconds to get the new code he committed, and it only takes a few minutes to compile SMPlayer, make packages and upload them.