Date: Wed, 01 Oct 2014 11:19:03 +0100 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> To: freebsd-ports@freebsd.org Cc: Enrico Maria Crisostomo <enrico.m.crisostomo@gmail.com> Subject: Re: Port Name Clash: What To Do? Message-ID: <5911568.kPDBkIzsi4@curlew.lan> In-Reply-To: <0A592A38-E61A-45B9-8D3C-63402102D8A0@gmail.com> References: <0A592A38-E61A-45B9-8D3C-63402102D8A0@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193721>; 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5911568.kPDBkIzsi4>