Date: Tue, 29 Nov 2016 19:16:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214675] [NEW PORT] net-mgmt/prometheus-collectd-exporter: Prometheus collectd exporter Message-ID: <bug-214675-13-29by59hS9L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214675-13@https.bugs.freebsd.org/bugzilla/> References: <bug-214675-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214675 jevonearth <ports@ecadlabs.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ports@ecadlabs.com --- Comment #1 from jevonearth <ports@ecadlabs.com> --- Hi, Some unsolicited notes, to help out a little, I ran this new port through poudriere testport, results are; 10.3-RELEASE-p12 amd64 pass 11.0-RELEASE-p3 amd64 pass 9.3-RELEASE-p50 amd64 pass @dsp@php.net running portlint on your new port generates two warnings, one (COMMENT should begin with a capital) is trivial to fix. The FreeBSD ports folk then to prefer patch files generated using `svn diff` these days (porters handbook should probably be updated, but that's another matter). I typically add the new port to svn local working directory and th= en run: sudo svn diff | sudo tee ../`make -VPKGNAME`.diff=20 from the directory of the port you are contributing. I did not perform any functional testing on the port, but I did notice that there is not rc script included. Hope this is helpful, Jev --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214675-13-29by59hS9L>