[MacPorts] #33489: MPlayer @1.0rc4 - hidden dependencies

[MacPorts]

#33489: MPlayer @1.0rc4 - hidden dependencies
----------------------------+-----------------------------------------------
  Reporter:  hans@…         |       Owner:  macports-tickets@…                   
      Type:  defect         |      Status:  closed                               
  Priority:  Normal         |   Milestone:                                       
 Component:  ports          |     Version:  2.0.4                                
Resolution:  fixed          |    Keywords:                                       
      Port:  MPlayer        |  
----------------------------+-----------------------------------------------
Changes (by ecronin@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Replying to [comment:3 hans@…]:
 >
 > The only reason why I am using MPlayer @1.0rc4, out of those three, is
 that "port install mplayer" is the first that comes to mind. I believe
 it's in the names of the ports, which seem to suggest (to me anyway):
 > {{{
 > mplayer  = the regular stuff
 > mplayer2 = new version, if you are adventurous
 > mplayer-devel = bleeding edge, if you are more adventurous
 > }}}

 The issue with mplayer is that the only thing supported by upstream is the
 bleeding edge.  They don't roll releases, they only put up patches to the
 most serious security issues, they tell you to go away unless you're
 running a SVN build from within the last few hours...  Our mplayer-devel
 port tries to strike a middle ground by picking a specific not too old svn
 revision, testing it out, and leaving it alone for a few months unless
 there's an issue that needs dealing with.  mplayer2 is a fairly new
 fork/rewrite and is the least mature of the three, I have no idea if it or
 mplayer-devel is preferable for the average user.  Unless they added it
 back recently, mplayer2 dropped mencoder entirely which makes it less
 useful to me.

 >
 > If the ports were named "mplayer1", "mplayer", "mplayer1-devel" (instead
 of, respectively, "mplayer", "mplayer2", "mplayer-devel"), I believe
 people would be just using MPlayer2, because that would be what the
 obvious "port install mplayer" would do.

 Yes, there are many things unfortunate about the port being named MPlayer
 (capitalization included), but renaming ports once they exist is
 complicated.  mplayer2 made things worse as it is a fork+rewrite of
 mplayer and not a new version of mplayer, both mplayer-devel and mplayer2
 are under active development.

 Going to close with the assumption r90448 took care of this.

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