Will be needed for forthcoming editors/pycharm. Redports: https://redports.org/buildarchive/20140909190501-15528/
Created attachment 147183 [details] Add fsnotifier
FYI: redports is now useless for QA testing but this is very simple port This line: "PLIST_FILES= bin/${PORTNAME} bin/${PORTNAME}64" Is unacceptable to me. If I change the name of the port, the port fails, yes? It's a huge pet peeve of mine to use PORTNAME like this, so I'm going to replace it with the current value of PORTNAME.
also, the procedure for submitting a new port involves providing a shar file, not a patch: https://www.freebsd.org/doc/en/books/porters-handbook/porting-submitting.html
The makefile didn't pass portlint (but easily fixed) and the pkg-descr is too skimpy. What is fsnotify? what is fsnotifier? why do people need it? FYI, "man fsnotify" comes up empty. I had to rewrite the comment to not use "fsnotifier" but I can't fix pkg-descr and I really think it needs a lot more detail.
Created attachment 148823 [details] Current version of port as fixed Here is the current version of the port. I removed the "id" stuff with uidfix, please let me know if you agree. I am also waiting on a better pkg-descr. When that comes, I'll commit this.
Hi melvyn, Did you get a notice for your PR? I'm waiting a response about the description file before I commit your port, which is already prepared. It's been a few days already. (on vacation perhaps?)
It does not bode well for this port is the proposed maintainer is unreachable before it's even committed. I'll wait for this a few more days, then I'm closing the PR without committing it.
Proposed maintainer is unreachable in reasonable amount of time. As we don't introduce unmaintained ports into the tree, I'm closing the PR without submitting it. I did update the shar, so it should be easy to resume later.