svn commit: r510437 - head/devel/rubygem-activejob4

[Sunpoet Po-Chuan Hsieh]

Author: sunpoet
Date: Sat Aug 31 21:57:40 2019
New Revision: 510437
URL: https://svnweb.freebsd.org/changeset/ports/510437

Log:
  Add PORTSCOUT
  
  - Update pkg-descr
  - Take maintainership

Modified:
  head/devel/rubygem-activejob4/Makefile
  head/devel/rubygem-activejob4/pkg-descr

Modified: head/devel/rubygem-activejob4/Makefile
==============================================================================
--- head/devel/rubygem-activejob4/Makefile	Sat Aug 31 21:57:35 2019	(r510436)
+++ head/devel/rubygem-activejob4/Makefile	Sat Aug 31 21:57:40 2019	(r510437)
@@ -7,7 +7,7 @@ CATEGORIES=	devel rubygems
 MASTER_SITES=	RG
 PKGNAMESUFFIX=	4
 
-MAINTAINER=	ruby at FreeBSD.org
+MAINTAINER=	sunpoet at FreeBSD.org
 COMMENT=	Job class declarations for a variety of queueing backends
 
 LICENSE=	MIT
@@ -20,5 +20,7 @@ USES=		gem
 USE_RUBY=	yes
 
 NO_ARCH=	yes
+
+PORTSCOUT=	limit:^4\.2\.
 
 .include <bsd.port.mk>

Modified: head/devel/rubygem-activejob4/pkg-descr
==============================================================================
--- head/devel/rubygem-activejob4/pkg-descr	Sat Aug 31 21:57:35 2019	(r510436)
+++ head/devel/rubygem-activejob4/pkg-descr	Sat Aug 31 21:57:40 2019	(r510437)
@@ -1,3 +1,19 @@
-Declare job classes that can be run by a variety of queueing backends.
+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, really.
 
+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 of
+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/master/activejob