BSD Ports

sysutils/rubygem-ohai 19.1.24 MidnightBSD

Ohai profiles your system and emits JSON

System
MidnightBSD
Repository
mports
Maintainer
[email protected]
Last update
Commit
f9d9b6565a
License
Apache-2.0
Categories
sysutils, rubygems

Description

Ohai detects data about your operating system. It can be used standalone, but it's primary purpose is to provide node data to Chef.

Ohai will print out a JSON data blob for all the known data about your system. When used with Chef, that data is reported back via node attributes.

In the other systems

SystemPortVersion
MidnightBSDsysutils/rubygem-ohai19.1.24
FreeBSDsysutils/rubygem-ohai19.1.40
DragonFlysysutils/rubygem-ohai18.1.18
HardenedBSDsysutils/rubygem-ohai19.1.40
GhostBSDsysutils/rubygem-ohai19.1.40

Install

Binary package:

mport install ohai

From mports:

cd /usr/mports/sysutils/rubygem-ohai && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	ohai>0:sysutils/rubygem-ohai

Dependencies

As this port's Makefile names them.

Build 13

Runtime 13

Build dependencies 13
Run dependencies 13

No port depends on this one.

Configuration

No options to configure.

USES
gem
Service scripts
none

Files

distinfo 1
FileSizeSHA256
rubygem/ohai-19.1.24.gem134656a15f3fd2298321a494c536a7af0e97020d71e4034963d42598bd4f33eacd7758
Master sites 1
  • RG

Commit history 1

DateCommitCreditsLog message
f9d9b6565a Lucas Holt sysutils/rubygem-ohai: install RUN_DEPENDS at build time
The gemdeps QA check runs ${LOCALBASE}/bin/gem list, so the runtime gems have to be installed before fake-qa. The build cluster installs BUILD_DEPENDS but not RUN_DEPENDS, so the check reported dependencies as unsatisfied even though they had built successfully in the same run. This matches the convention already used by most rubygem ports. AI-Assisted-by: Claude Opus 5 (1M context) <[email protected]> Signed-off-by: Lucas Holt <[email protected]>