Port Name Clash: What To Do?

[Enrico Maria Crisostomo]

Thank you very much Mike,

I’ll have a look at that PR ASAP.

Cheers,
-- 
Enrico Maria Crisostomo

On 1 Oct 2014 at 12:19:06, Mike Clarke (jmc-freebsd2 at milibyte.co.uk) wrote:

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