[MacPorts] #30279: MPlayer @1.0rc4, Revision 1 fails with clang, llvm-gcc-4.2, Lion

[MacPorts]

#30279: MPlayer @1.0rc4, Revision 1 fails with clang, llvm-gcc-4.2, Lion
------------------------------------------+---------------------------------
  Reporter:  j_mach_wust@…                |       Owner:  macports-tickets@…                   
      Type:  defect                       |      Status:  closed                               
  Priority:  Normal                       |   Milestone:                                       
 Component:  ports                        |     Version:  1.9.2                                
Resolution:  fixed                        |    Keywords:  lion                                 
      Port:  MPlayer                      |  
------------------------------------------+---------------------------------

Comment(by ecronin@…):

 The developers of mplayer have been pretty emphatic that they see no need
 to roll releases, it's just extra work for them.  We're not the only
 package maintainers who have complained, but that policy doesn't seem to
 be changing.  They won't even entertain bug reports unless you're running
 that moments latest TRUNK.  So realistically there will never be a stable
 mplayer again.  1.0rc4 isn't even stable, it's just stable-ish five years
 ago before they gave up on even making versioned tarballs.

 I don't maintain the -devel port, but my experience has been that it is
 updated to a known-unbroken-at-the-time svn/git tag at a fairly infrequent
 pace, and the upgrades themselves are never what breaks- it's os x or
 other libraries changing underneath that cause issues.  When these happen
 the mplayer trunk is usually fixed quickly and the -devel port bumped to a
 newer tag.

 Upstream isn't making any bugfixes to mplayer 1.0rcX (even critical
 security anymore it seems) and it's getting more challenging to keep it
 running as the rest of the world moves forward (hence this ticket taking 3
 months to resolve).  Were this a good solid 1.0+ version before they went
 off and rewrote everything maybe it would make sense to keep it alive.
 But it's just another point in an always unstable code base that's
 artificially alive because it was the last time they slapped a tag on a
 specific revision of the source code...

 So yes, ideally, it would be bad to recommend running a -devel port as the
 best most stable version.  But mplayer is not ideal software...
 Eventually what is now mplayer-devel should probably become the new
 mplayer (perhaps solving the annoying capitalized portname finally too)
 and we just admit that the 'stable' version is a specific revision of the
 development branch because upstream has no notion of a stable release.

-- 
Ticket URL: <https://trac.macports.org/ticket/30279#comment:26>
MacPorts <http://www.macports.org/>
Ports system for Mac OS