| Port details |
- rubygem-opentelemetry-registry Registry for the OpenTelemetry Instrumentation libraries
- 0.3.1 devel
 =2      0.3.1Version of this port present on the latest quarterly branch. - Maintainer: sunpoet@FreeBSD.org
- Port Added: 2023-10-16 16:04:01
- Last Update: 2024-03-31 03:08:58
- Commit Hash: a4c6176
- People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py39-PyOpenGL, p5-Sane
- Also Listed In: rubygems
- License: APACHE20
- WWW:
- https://opentelemetry.io/
- https://github.com/open-telemetry/opentelemetry-ruby
- https://github.com/open-telemetry/opentelemetry-ruby/tree/main/registry
- 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.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- rubygem-opentelemetry-registry>0:devel/rubygem-opentelemetry-registry
- To install the port:
- cd /usr/ports/devel/rubygem-opentelemetry-registry/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/rubygem-opentelemetry-registry
- pkg install rubygem-opentelemetry-registry
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: rubygem-opentelemetry-registry
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1711466366
SHA256 (rubygem/opentelemetry-registry-0.3.1.gem) = 73a48234635b0ed1c75e4b5fb267fb3004baf616d43fe38e8380ecbb933d88df
SIZE (rubygem/opentelemetry-registry-0.3.1.gem) = 10752
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
- Runtime dependencies:
-
- rubygem-opentelemetry-api>=1.1<2 : devel/rubygem-opentelemetry-api
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
- Patch dependencies:
-
- ruby32 : lang/ruby32
- gem : devel/ruby-gems
-
- This port is required by:
- for Run
-
- devel/rubygem-opentelemetry-instrumentation-base
- devel/rubygem-opentelemetry-sdk
Configuration Options:- No options to configure
- Options name:
- devel_rubygem-opentelemetry-registry
- USES:
- gem
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
0.3.1
31 Mar 2024 03:08:58
 |
Po-Chuan Hsieh (sunpoet) |
devel/rubygem-opentelemetry-registry: Update to 0.3.1
Changes: https://github.com/open-telemetry/opentelemetry-ruby/releases
https://github.com/open-telemetry/opentelemetry-ruby/blob/main/registry/CHANGELOG.md |
0.3.0
16 Oct 2023 15:59:40
|
Po-Chuan Hsieh (sunpoet) |
devel/rubygem-opentelemetry-registry: Add rubygem-opentelemetry-registry 0.3.0
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. |
As an Amazon Associate I earn from qualifying purchases.