From owner-freebsd-ports Tue May 29 3:31:46 2001 Delivered-To: freebsd-ports@freebsd.org Received: from iraun1.uka.de (iraun1.uka.de [129.13.10.90]) by hub.freebsd.org (Postfix) with ESMTP id AE42C37B43C for ; Tue, 29 May 2001 03:31:39 -0700 (PDT) (envelope-from esk@ira.uka.de) Received: from i30nb2.ira.uka.de by iraun1 (PP) with ESMTP; Tue, 29 May 2001 12:31:33 +0200 Received: (from esk@localhost) by i30nb2.ira.uka.de (8.11.2/8.11.3) id f4TAVUf12375; Tue, 29 May 2001 12:31:30 +0200 (CEST) (envelope-from esk) From: Espen Skoglund MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15123.31361.988389.672402@i30nb2.ira.uka.de> Date: Tue, 29 May 2001 12:31:29 +0200 (CEST) To: freebsd-ports@FreeBSD.ORG Subject: Re: Maintainer note: Please commit ports/27453 In-Reply-To: <15122.34649.427846.394028@i30nb2.ira.uka.de> References: <15122.34649.427846.394028@i30nb2.ira.uka.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [Espen Skoglund] > The following PR fixes an mtree problem with devel/arm-elf-gcc295: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/27453 Uhm, wait a minute, it seems that the file added to the plist (bin/arm-elf-c++filt) was also part of arm-elf-binutils. What should one do when there are conflicts like this? Should I: a) Ignore the file in the gcc plist. This will somehow work since gcc depends on binutils anyway. It will create errorlogs on bento, though, and it seems like the wrong thing to do since it will possibly leave you with files in the system which are unaccounted for. b) Add it to the gcc plist, remove it from the binutils plist, and manually remove the file from the file system after make install in arm-elf-binutils. Since arm-elf-gcc295 is probably the only port which will ever need this file, this seems like a working solution. It does, however, create a few problems if you reinstall binutils after gcc has been installed (i.e., file will be deleted). c) Have the file in both plists. Easiest solution. Will ``break'' binutils if gcc is removed from the system. If gcc is removed on the other hand, there is probably no other port using binutils anyway. Comments? eSk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message