What the hell is going on with mplayer?

[Simon L. Nielsen]

On 2006.07.13 10:16:27 -0500, Brooks Davis wrote:
> On Thu, Jul 13, 2006 at 04:35:15PM +0200, Alexander Leidinger wrote:
> > Quoting Heino Tiedemann <rotkaps_spam_trap at gmx.de> (from Thu, 13 Jul  
> > 2006 15:23:07 +0200):
> > 
> > >I just wanted to so a simple ??portupgrade mplayer-gtk??, and see what
> > >habens:
> > >
> > >
> > >** Detected a package name change: mplayer-gtk (multimedia/mplayer)   
> > >-> 'mplayer-gtk2-esound' (multimedia/mplayer)
> > >                    ^^^^^^^^^^^^^^^^^^^
> > >                    What a surprise, name change. Not mentioned in UPDATING
> > 
> > Does it needs to be mentioned? portupgrade is able to handle it  
> > without *special* instructions in UPDATING.
> 
> This port should not set its name based on configured (or in this case
> automagicaly detected and thus ever changing) features unless it does so
> as part of a slave port.  This has been a minor annoyance for ages.  The
> port should be named mplayer, always.

Yes, please!

Ports which change their name are very annoying, especially for people
working with VuXML since we have to list all possible names there.

When there is a 1-to-1 mapping of possible names and slave ports, then
it's no problem, it's the other ones that are painful...

I just haven't had the energy to really take this up with the
maintainers for the ports that does this.

-- 
Simon L. Nielsen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20060713/de2a6216/attachment.pgp