Date: Sat, 23 Jan 2016 16:12:13 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 206526] [NEW PORT] comms/openzwave: Open-source interface to Z-Wave networks Message-ID: <bug-206526-13-DzIpEXIPDW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206526-13@https.bugs.freebsd.org/bugzilla/> References: <bug-206526-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=3D206526 --- Comment #5 from johan@stromnet.se --- portlint -AC did not warn on 'Open-zwave - An open-source...', but it *does* warn on 'An open-source...'. Fixed. Hm, actually I missed the fact that there where release tarballs (which *do= es* have revision, even a 1.4.1 which there is no tag for). I've been running a local openzwave-devel port which fetched from GH before, so this one was ba= sed on that. Will check the tarballs instead, and also investigate what 1.4.1 h= as that 1.4.0 lacks, and which one corresponds to v1.4 tag on GH. Ah, will fix the portdocs things.=20 One more thing: is it recommended/required to have DOCS enabled by default?= On this port, it requires that both doxygen and graphiviz is installed, making= the build a looooot heavier in terms of build-deps. Will look into the details tomorrow. Thanks for very quick feedback! Regards Johan --=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-206526-13-DzIpEXIPDW>