From owner-freebsd-ports-bugs@FreeBSD.ORG Tue May 20 18:20:01 2014 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EF69E64 for ; Tue, 20 May 2014 18:20:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0538F21AB for ; Tue, 20 May 2014 18:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4KIK0nH003856 for ; Tue, 20 May 2014 18:20:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4KIK0Q3003855; Tue, 20 May 2014 18:20:00 GMT (envelope-from gnats) Resent-Date: Tue, 20 May 2014 18:20:00 GMT Resent-Message-Id: <201405201820.s4KIK0Q3003855@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "Ronald F.Guilmette" Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DE218A54 for ; Tue, 20 May 2014 18:10:18 +0000 (UTC) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id C33EE20EF for ; Tue, 20 May 2014 18:10:17 +0000 (UTC) Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id 95BF63AEBE; Tue, 20 May 2014 11:10:16 -0700 (PDT) Message-Id: <20140520181016.95BF63AEBE@segfault.tristatelogic.com> Date: Tue, 20 May 2014 11:10:16 -0700 (PDT) From: "Ronald F.Guilmette" Reply-To: "Ronald F.Guilmette" To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: ports/190027: mplayer & mplayer2 install conflict Cc: rfg@tristatelogic.com X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 18:20:01 -0000 >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: