Date: Tue, 20 May 2014 11:10:16 -0700 (PDT) From: "Ronald F.Guilmette" <rfg@tristatelogic.com> To: FreeBSD-gnats-submit@freebsd.org Cc: rfg@tristatelogic.com Subject: ports/190027: mplayer & mplayer2 install conflict Message-ID: <20140520181016.95BF63AEBE@segfault.tristatelogic.com> Resent-Message-ID: <201405201820.s4KIK0Q3003855@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 190027 >Category: ports >Synopsis: mplayer & mplayer2 install conflict >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 20 18:20:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: FreeBSD 9.1-RELEASE amd64 >Organization: entr0py >Environment: 9.1-RELEASE amd64 >Description: It appears that both the multimedia/mplayer port and the multimedia/mplayer2 ports will both attempt to install a file called "/usr/local/bin/mplayer". Because of this, if a user has one or the other of these ports installed, and then also attempts to install the other port, the second install will wipe out and overwrite the version of /usr/local/bin/mplayer that is part of the first installed port, and I believe that it does so WITHOUT first properly deregistering and de-installing that first installed port. The result will be a mess in which both ports _appear_ to currently be propely installed, but in fact only one of them is, and the other port is effectively corrupted. >How-To-Repeat: cd /usr/ports/multimedia/mplayer2 make install ls -l /usr/local/bin/mplayer cd /usr/ports/multimedia/mplayer make install ls -l /usr/local/bin/mplayer >Fix: Obviously, the main executable that is installed when the mplayer2 port is installed should be named "mplayer2", or ay any rate it should be named *something* that will not conflict with any installed files belonging to the mplayer (1) port. I have not looked to see how this may be accomplished within the relevant Makefiles, but I doubt that it would be difficult to do. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140520181016.95BF63AEBE>