From owner-freebsd-ports@FreeBSD.ORG Wed Oct 1 10:22:16 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 810473B3 for ; Wed, 1 Oct 2014 10:22:16 +0000 (UTC) Received: from avasout06.plus.net (avasout06.plus.net [212.159.14.18]) by mx1.freebsd.org (Postfix) with ESMTP id 169ECC64 for ; Wed, 1 Oct 2014 10:22:15 +0000 (UTC) Received: from curlew.milibyte.co.uk ([84.92.153.232]) by avasout06 with smtp id xmK51o008516WCc01mK6XZ; Wed, 01 Oct 2014 11:19:06 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=HNxNF+dv c=1 sm=1 tr=0 a=lfSX4pPLp9EkufIcToJk/A==:117 a=lfSX4pPLp9EkufIcToJk/A==:17 a=D7rCoLxHAAAA:8 a=0Bzu9jTXAAAA:8 a=PBtdaOD29JoA:10 a=ZTb9aqGL9YkA:10 a=8nJEP1OIZ-IA:10 a=NEAV23lmAAAA:8 a=6I5d2MoRAAAA:8 a=SJI-n6VokPetgGKQn-gA:9 a=wPNLvfGTeEIA:10 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.84) (envelope-from ) id 1XZGzw-00077I-RL; Wed, 01 Oct 2014 11:19:05 +0100 From: Mike Clarke To: freebsd-ports@freebsd.org Date: Wed, 01 Oct 2014 11:19:03 +0100 Message-ID: <5911568.kPDBkIzsi4@curlew.lan> User-Agent: KMail/4.12.5 (FreeBSD/9.3-RELEASE-p2; KDE/4.12.5; amd64; ; ) In-Reply-To: <0A592A38-E61A-45B9-8D3C-63402102D8A0@gmail.com> References: <0A592A38-E61A-45B9-8D3C-63402102D8A0@gmail.com> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Subject: Re: Port Name Clash: What To Do? Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="iso-8859-1" X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) Cc: Enrico Maria Crisostomo X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 10:22:16 -0000 On Wednesday 01 Oct 2014 11:54:36 Enrico Maria Crisostomo wrote: > I'm the author of fswatch (https://github.com/emcrisostomo/fswatch), > a cross-platform file change monitor, and I would like to submit a > new port for it. The port is ready (kudos to the FreeBSD community > for the high-quality documentation available) but I have not > submitted yet because I discovered that there exists another port > with the same name: security/fswatch. > > I'm now wondering what to do. I could rename the port itself but a > problem would remain: two different ports would contain files with > the same name. In fact, the two ports clash on one file: Until recently there was a port called filtermail which was renamed from mailfilter due to a name conflict. It was recently deleted due to not being staged but I recently got it working again and submitted a PR suggesting that my modified version of the original port might be reinstated in the ports tree. I don't know if that will happen or not but if you look at the makefile attached to the PR you might be able to use the same technique for renaming the port and relevant files. -- Mike Clarke