notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

Port details
rubygem-opentelemetry-registry Registry for the OpenTelemetry Instrumentation libraries
0.3.1 devel on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout 0.3.0Version of this port present on the latest quarterly branch.
Maintainer: sunpoet@FreeBSD.org search for ports maintained by this maintainer
Port Added: 2023-10-16 16:04:01
Last Update: 2024-03-31 03:08:58
Commit Hash: a4c6176
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.
HomepageHomepageHomepage    cgit ¦ Codeberg ¦ GitHub ¦ GitLab ¦ SVNWeb - no subversion history for this port

Manual pages:
FreshPorts has no man page information for this port.
pkg-plist: as obtained via: make generate-plist
Expand this list (3 items)
Collapse this list.
  1. /usr/local/share/licenses/rubygem-opentelemetry-registry-0.3.1/catalog.mk
  2. /usr/local/share/licenses/rubygem-opentelemetry-registry-0.3.1/LICENSE
  3. /usr/local/share/licenses/rubygem-opentelemetry-registry-0.3.1/APACHE20
Collapse this list.
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):
rubygem-opentelemetry-registry
ABIaarch64amd64armv6armv7i386powerpcpowerpc64powerpc64le
FreeBSD:13:latest0.3.10.3.1-0.3.10.3.1---
FreeBSD:13:quarterly0.3.10.3.1-0.3.10.3.10.3.00.3.00.3.0
FreeBSD:14:latest0.3.10.3.1-0.3.10.3.1---
FreeBSD:14:quarterly0.3.10.3.1-0.3.10.3.10.3.00.3.00.3.0
FreeBSD:15:latest0.3.10.3.1n/a0.3.0n/a0.3.00.3.00.3.0
Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. ruby32 : lang/ruby32
  2. gem : devel/ruby-gems
Runtime dependencies:
  1. rubygem-opentelemetry-api>=1.1<2 : devel/rubygem-opentelemetry-api
  2. ruby32 : lang/ruby32
  3. gem : devel/ruby-gems
Patch dependencies:
  1. ruby32 : lang/ruby32
  2. gem : devel/ruby-gems
Extract dependencies:
  1. ruby32 : lang/ruby32
This port is required by:
for Run
  1. devel/rubygem-opentelemetry-instrumentation-base
  2. 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:
Expand this list (1 items)
Collapse this list.
  1. https://rubygems.org/downloads/
Collapse this list.

Number of commits found: 2

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
0.3.1
31 Mar 2024 03:08:58
commit hash: a4c61768892d8dc99806b5f5400ed9e5b9181bc4commit hash: a4c61768892d8dc99806b5f5400ed9e5b9181bc4commit hash: a4c61768892d8dc99806b5f5400ed9e5b9181bc4commit hash: a4c61768892d8dc99806b5f5400ed9e5b9181bc4 files touched by this commit
Po-Chuan Hsieh (sunpoet) search for other commits by this committer
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
commit hash: 53adcca119ecee7f4764c5b809f9c9ad918543a0commit hash: 53adcca119ecee7f4764c5b809f9c9ad918543a0commit hash: 53adcca119ecee7f4764c5b809f9c9ad918543a0commit hash: 53adcca119ecee7f4764c5b809f9c9ad918543a0 files touched by this commit
Po-Chuan Hsieh (sunpoet) search for other commits by this committer
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.

Number of commits found: 2