Date: Fri, 14 Dec 2018 10:46:48 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 234007] [NEW PORT] irc/bitlbee-discord: Discord plugin for bitlbee Message-ID: <bug-234007-7788-5zateI39SD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234007-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-234007-7788@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=3D234007 --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Arthur Pirika from comment #3) VM's are perfectly fine (I do mine in a virtualbox CURRENT guest), and its = good to know you've run through portlint/poudriere. For future issues, its always good to mention this explicitly, so there's no questions or ambiguity, like: portlint: OK (looks fine.) testport: OK (poudriere: <versions, archs> tested) Unless the software has a test suite, and the port has TEST_DEPENDS (if necessary) and a test: target to run the tests, poudriere (in various architecture/version jails) basically tests everything up to and including packaging (fetch, configure build, install), but not runtime, which is why = test suite integration is fantastic if upstream provides them. You can mention t= his in your issues, like: maketest: OK (XXX of YYY tests: PASS) For some mode 101/cheatsheets/guidelines on Porting/Bugzilla/Workflow: * https://wiki.freebsd.org/KubilayKocak/ThePerfectPortsIssue * https://wiki.freebsd.org/KubilayKocak/Bugzilla/DosAndDonts --=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-234007-7788-5zateI39SD>