git: bb31a5cde5bb - main - devel/rubygem-activejob70: Add rubygem-activejob70 7.0.0
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 11 Jan 2022 18:52:43 UTC
The branch main has been updated by sunpoet:
URL: https://cgit.FreeBSD.org/ports/commit/?id=bb31a5cde5bb0395f58209fbc5220c5d2a2b0a6b
commit bb31a5cde5bb0395f58209fbc5220c5d2a2b0a6b
Author: Po-Chuan Hsieh <sunpoet@FreeBSD.org>
AuthorDate: 2022-01-11 16:56:47 +0000
Commit: Po-Chuan Hsieh <sunpoet@FreeBSD.org>
CommitDate: 2022-01-11 18:43:51 +0000
devel/rubygem-activejob70: Add rubygem-activejob70 7.0.0
Active Job is a framework for declaring jobs and making them run on a variety of
queuing backends. These jobs can be everything from regularly scheduled
clean-ups, to billing charges, to mailings -- anything that can be chopped up
into small units of work and run in parallel.
It also serves as the backend for Action Mailer's #deliver_later functionality
that makes it easy to turn any mailing into a job for running later. That's one
of the most common jobs in a modern web application: sending emails outside the
request-response cycle, so the user doesn't have to wait on it.
The main point is to ensure that all Rails apps will have a job infrastructure
in place, even if it's in the form of an "immediate runner". We can then have
framework features and other gems build on top of that, without having to worry
about API differences between Delayed Job and Resque. Picking your queuing
backend becomes more of an operational concern, then. And you'll be able to
switch between them without having to rewrite your jobs.
WWW: https://rubyonrails.org/
WWW: https://github.com/rails/rails/tree/main/activejob
---
devel/Makefile | 1 +
devel/rubygem-activejob70/Makefile | 26 ++++++++++++++++++++++++++
devel/rubygem-activejob70/distinfo | 3 +++
devel/rubygem-activejob70/pkg-descr | 19 +++++++++++++++++++
4 files changed, 49 insertions(+)
diff --git a/devel/Makefile b/devel/Makefile
index 1001e9a2cf77..d68e42d44306 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -5652,6 +5652,7 @@
SUBDIR += rubygem-activejob52
SUBDIR += rubygem-activejob60
SUBDIR += rubygem-activejob61
+ SUBDIR += rubygem-activejob70
SUBDIR += rubygem-activemessaging
SUBDIR += rubygem-activerecord-deprecated_finders
SUBDIR += rubygem-activesupport4
diff --git a/devel/rubygem-activejob70/Makefile b/devel/rubygem-activejob70/Makefile
new file mode 100644
index 000000000000..55d744afd38a
--- /dev/null
+++ b/devel/rubygem-activejob70/Makefile
@@ -0,0 +1,26 @@
+PORTNAME= activejob
+PORTVERSION= 7.0.0
+CATEGORIES= devel rubygems
+MASTER_SITES= RG
+PKGNAMESUFFIX= 70
+
+MAINTAINER= sunpoet@FreeBSD.org
+COMMENT=
+
+LICENSE= MIT
+LICENSE_FILE= ${WRKSRC}/MIT-LICENSE
+
+RUN_DEPENDS= rubygem-activesupport70>=${PORTVERSION}:devel/rubygem-activesupport70 \
+ rubygem-globalid-rails70>=0.3.6:databases/rubygem-globalid-rails70
+
+USES= cpe gem
+USE_RUBY= yes
+
+NO_ARCH= yes
+
+CPE_VENDOR= rubyonrails
+CPE_PRODUCT= active_job
+
+PORTSCOUT= limit:^7\.0\.
+
+.include <bsd.port.mk>
diff --git a/devel/rubygem-activejob70/distinfo b/devel/rubygem-activejob70/distinfo
new file mode 100644
index 000000000000..6a7dc122ccc3
--- /dev/null
+++ b/devel/rubygem-activejob70/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1641045760
+SHA256 (rubygem/activejob-7.0.0.gem) = dfd0e1d050b2adda91158db1061b9f28835740c84cbc9b009617f4b240922dbb
+SIZE (rubygem/activejob-7.0.0.gem) = 32768
diff --git a/devel/rubygem-activejob70/pkg-descr b/devel/rubygem-activejob70/pkg-descr
new file mode 100644
index 000000000000..d21b21013131
--- /dev/null
+++ b/devel/rubygem-activejob70/pkg-descr
@@ -0,0 +1,19 @@
+Active Job is a framework for declaring jobs and making them run on a variety of
+queuing backends. These jobs can be everything from regularly scheduled
+clean-ups, to billing charges, to mailings -- anything that can be chopped up
+into small units of work and run in parallel.
+
+It also serves as the backend for Action Mailer's #deliver_later functionality
+that makes it easy to turn any mailing into a job for running later. That's one
+of the most common jobs in a modern web application: sending emails outside the
+request-response cycle, so the user doesn't have to wait on it.
+
+The main point is to ensure that all Rails apps will have a job infrastructure
+in place, even if it's in the form of an "immediate runner". We can then have
+framework features and other gems build on top of that, without having to worry
+about API differences between Delayed Job and Resque. Picking your queuing
+backend becomes more of an operational concern, then. And you'll be able to
+switch between them without having to rewrite your jobs.
+
+WWW: https://rubyonrails.org/
+WWW: https://github.com/rails/rails/tree/main/activejob