Date: Wed, 1 Oct 2014 12:56:18 +0200 From: Enrico Maria Crisostomo <enrico.m.crisostomo@gmail.com> To: freebsd-ports@freebsd.org, Mike Clarke <jmc-freebsd2@milibyte.co.uk> Subject: Re: Port Name Clash: What To Do? Message-ID: <etPan.542bddd3.238e1f29.de06@MacBook0.local> In-Reply-To: <5911568.kPDBkIzsi4@curlew.lan> References: <0A592A38-E61A-45B9-8D3C-63402102D8A0@gmail.com> <5911568.kPDBkIzsi4@curlew.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you very much Mike, I=E2=80=99ll have a look at that PR ASAP. Cheers, --=C2=A0 Enrico Maria Crisostomo On 1 Oct 2014 at 12:19:06, Mike Clarke (jmc-freebsd2=40milibyte.co.uk) wr= ote: On Wednesday 01 Oct 2014 11:54:36 Enrico Maria Crisostomo wrote: =20 > I'm the author of fswatch (https://github.com/emcrisostomo/fswatch), =20 > a cross-platform file change monitor, and I would like to submit a =20 > new port for it. The port is ready (kudos to the =46reeBSD community =20 > for the high-quality documentation available) but I have not =20 > submitted yet because I discovered that there exists another port =20 > with the same name: security/fswatch. =20 > =20 > I'm now wondering what to do. I could rename the port itself but a =20 > problem would remain: two different ports would contain files with =20 > the same name. In fact, the two ports clash on one file: =20 Until recently there was a port called filtermail which was renamed =20 from mailfilter due to a name conflict. It was recently deleted due to =20 not being staged but I recently got it working again and submitted a =20 PR <https://bugs.freebsd.org/bugzilla/show=5Fbug.cgi=3Fid=3D193721>; =20 suggesting that my modified version of the original port might be =20 reinstated in the ports tree. I don't know if that will happen or not =20 but if you look at the makefile attached to the PR you might be able =20 to use the same technique for renaming the port and relevant files. =20 -- =20 Mike Clarke =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?etPan.542bddd3.238e1f29.de06>