BSD Ports

devel/rubygem-opentelemetry-registry 0.5.0 MidnightBSD

Registry for the OpenTelemetry Instrumentation libraries

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

Description

The instrumentation Registry contains information about available instrumentation, facilitates discovery, installation, and configuration.

The Registry allows for instrumentation to avoid depending directly on a specific SDK implementation.

The SDK depends on the Registry, the instrumentation Base class depends on the Registry, and auto instrumentation libraries extend the instrumentation Base class.

The motivation for decoupling the Registry (and by extension the instrumentation) from a specific SDK implementation means that anyone can implement their own OpenTelemetry API compatible SDK, and they could continue to use community made instrumentation.

In the other systems

SystemPortVersion
MidnightBSDdevel/rubygem-opentelemetry-registry0.5.0
FreeBSDdevel/rubygem-opentelemetry-registry0.6.3
DragonFlydevel/rubygem-opentelemetry-registry0.4.0
HardenedBSDdevel/rubygem-opentelemetry-registry0.6.3
GhostBSDdevel/rubygem-opentelemetry-registry0.6.3

Install

Binary package:

mport install opentelemetry-registry

From mports:

cd /usr/mports/devel/rubygem-opentelemetry-registry && make install clean

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

RUN_DEPENDS=	opentelemetry-registry>0:devel/rubygem-opentelemetry-registry

Dependencies

As this port's Makefile names them.

Build 1

Runtime 1

Build dependencies 1
Run dependencies 1

Configuration

No options to configure.

USES
gem
Service scripts
none

Files

distinfo 1
FileSizeSHA256
rubygem/opentelemetry-registry-0.5.0.gem10752726ca58ada93a23efaa5f7bb81b8ab7a8a1e14602935c9c65dfa2e597a19fb4f
Master sites 1
  • RG

Commit history 1

DateCommitCreditsLog message
c9039dfd2f Lucas Holt devel/rubygem-opentelemetry-registry: 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]>