Port Name Clash: What To Do?

Enrico Maria Crisostomo enrico.m.crisostomo at gmail.com
Wed Oct 1 09:54:44 UTC 2014


Hi all,

I'm re-posting to this mailing list a question I asked in the FreeBSD forums, as suggested by a user (DutchDaemon).

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:

man/man7/fswatch.7.gz

A man page is not a great deal, but it may be a symptom of worse problems to come.

Can you share your thoughts on this? What would you do? Does it sound good to you to mark my port in conflict with the other one (I tried with CONFLICTS= but could not figure out the proper way to do it, since both packages' name start with fswatch-)?

Thanks for sharing.

Cheers,
-- Enrico
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4142 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20141001/3b946cd2/attachment.bin>


More information about the freebsd-ports mailing list