"make plist" to create the base PLIST file, and add @sample lines to create
the directories, also either "@extra (file)" or "@extraunexec rm -r
(path)/*" to cover files that night be created at runtime so that
pkg_delete -c is able to remove them.
--
Sent from a phone, apologies for poor
I’ve gotten to the stage where I need to create the plist for netdata. (I
haven’t touched any of the plugins yet; I want to package it so I can cleanly
install/deinstall it and verify that I haven’t broken anything.) The project’s
makefile creates a few directories in /var/lib that merely
> On 10 Sep, 2018, at 05:50, Stuart Henderson wrote:
>
> It's not going to be the simplest first port (it will need actual code
> porting, rather than just writing ports Makefile etc).
Yeah, I’ve already run into a few of these.
> Many of the Linux-ish plugins use procfs which isn't very
On 2018/09/09 20:04, William Leuschner wrote:
> Hello ports@,
>
> I’m quite pleased with netdata (https://my-netdata.io) as a monitoring
> tool on my non-OpenBSD boxes, and I’d like to port it over. The
> project’s GitHub page has a few issues mentioning OpenBSD in passing,
> but nothing about
Hello ports@,
I’m quite pleased with netdata (https://my-netdata.io) as a monitoring tool on
my non-OpenBSD boxes, and I’d like to port it over. The project’s GitHub page
has a few issues mentioning OpenBSD in passing, but nothing about porting it.
Before I get too far into the weeds, is
