Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Sep 2016 23:01:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 210545] [NEW PORT] devel/riemann-c-client: C client library for the Riemann monitoring system
Message-ID:  <bug-210545-13-WryFEFd2sY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210545-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-210545-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=3D210545

--- Comment #6 from Dave Cottlehuber <dch@skunkwerks.at> ---
It seems this is a very popular port now that we all need it for collectd5.=
6...
sorry for the double work, I didn't see this ticket til now.

I got all the FreeBSD issues resolved upstream today, and released as 1.9.1
which means we don't need to carry any patches - yay.

Some comments especially focused on the use of this as a command-line tool,=
 and
not just a development library for other things like collectd:

Due to POLA principle, I'm not in favour of having JSON-C and Gnu-TLS as
optional as the riemann-client command-line tool is then severely limited in
functionality. Riemann with TLS support is very common in the wild, and JSO=
N is
almost essential these days. The command-line tool terminates with a .so er=
ror
if JSON-C is not available. Not classy!

# QA for my build
- passes portlint -AC
- poudriere 11.0Rp0 amd64 is ok, waiting on the rest as my buildbot is occu=
pied

BTW as maintainer for net-mgmt/riemann itself, I'd be happy to maintain this
port too, unless somebody else prefers to, irrespective of what patches end=
 up
going in.

--=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-210545-13-WryFEFd2sY>