git: 53adcca119ec - main - devel/rubygem-opentelemetry-registry: Add rubygem-opentelemetry-registry 0.3.0

From: Po-Chuan Hsieh <sunpoet_at_FreeBSD.org>
Date: Mon, 16 Oct 2023 16:00:36 UTC
The branch main has been updated by sunpoet:

URL: https://cgit.FreeBSD.org/ports/commit/?id=53adcca119ecee7f4764c5b809f9c9ad918543a0

commit 53adcca119ecee7f4764c5b809f9c9ad918543a0
Author:     Po-Chuan Hsieh <sunpoet@FreeBSD.org>
AuthorDate: 2023-10-16 15:11:25 +0000
Commit:     Po-Chuan Hsieh <sunpoet@FreeBSD.org>
CommitDate: 2023-10-16 15:59:40 +0000

    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.
---
 devel/Makefile                                 |  1 +
 devel/rubygem-opentelemetry-registry/Makefile  | 21 +++++++++++++++++++++
 devel/rubygem-opentelemetry-registry/distinfo  |  3 +++
 devel/rubygem-opentelemetry-registry/pkg-descr | 14 ++++++++++++++
 4 files changed, 39 insertions(+)

diff --git a/devel/Makefile b/devel/Makefile
index d4b2b2b2f383..402790117f09 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -7117,6 +7117,7 @@
     SUBDIR += rubygem-opentelemetry-api
     SUBDIR += rubygem-opentelemetry-common
     SUBDIR += rubygem-opentelemetry-instrumentation-base
+    SUBDIR += rubygem-opentelemetry-registry
     SUBDIR += rubygem-opentracing
     SUBDIR += rubygem-opt_parse_validator
     SUBDIR += rubygem-optimist
diff --git a/devel/rubygem-opentelemetry-registry/Makefile b/devel/rubygem-opentelemetry-registry/Makefile
new file mode 100644
index 000000000000..eaa043e01b39
--- /dev/null
+++ b/devel/rubygem-opentelemetry-registry/Makefile
@@ -0,0 +1,21 @@
+PORTNAME=	opentelemetry-registry
+PORTVERSION=	0.3.0
+CATEGORIES=	devel rubygems
+MASTER_SITES=	RG
+
+MAINTAINER=	sunpoet@FreeBSD.org
+COMMENT=	Registry for the OpenTelemetry Instrumentation libraries
+WWW=		https://opentelemetry.io/ \
+		https://github.com/open-telemetry/opentelemetry-ruby \
+		https://github.com/open-telemetry/opentelemetry-ruby/tree/main/registry
+
+LICENSE=	APACHE20
+LICENSE_FILE=	${WRKSRC}/LICENSE
+
+RUN_DEPENDS=	rubygem-opentelemetry-api>=1.1<2:devel/rubygem-opentelemetry-api
+
+USES=		gem
+
+NO_ARCH=	yes
+
+.include <bsd.port.mk>
diff --git a/devel/rubygem-opentelemetry-registry/distinfo b/devel/rubygem-opentelemetry-registry/distinfo
new file mode 100644
index 000000000000..cfc0f0207b84
--- /dev/null
+++ b/devel/rubygem-opentelemetry-registry/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1697463044
+SHA256 (rubygem/opentelemetry-registry-0.3.0.gem) = 116ab6114a706340900718298c126f720e50b1ef3cfdbe5997611ff232fe6822
+SIZE (rubygem/opentelemetry-registry-0.3.0.gem) = 10752
diff --git a/devel/rubygem-opentelemetry-registry/pkg-descr b/devel/rubygem-opentelemetry-registry/pkg-descr
new file mode 100644
index 000000000000..9a740f141cdb
--- /dev/null
+++ b/devel/rubygem-opentelemetry-registry/pkg-descr
@@ -0,0 +1,14 @@
+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.