git: 813ebdcd1b9f - main - devel/R-cran-future.apply: Add new port

[TAKATSU Tomonari]

The branch main has been updated by tota:

URL: https://cgit.FreeBSD.org/ports/commit/?id=813ebdcd1b9f76358aefedb5ba70afd8a6caceb9

commit 813ebdcd1b9f76358aefedb5ba70afd8a6caceb9
Author:     TAKATSU Tomonari <tota at FreeBSD.org>
AuthorDate: 2021-09-08 11:08:37 +0000
Commit:     TAKATSU Tomonari <tota at FreeBSD.org>
CommitDate: 2021-09-08 11:43:39 +0000

    devel/R-cran-future.apply: Add new port
    
    Implementations of apply(), by(), eapply(), lapply(), Map(),
    .mapply(), mapply(), replicate(), sapply(), tapply(), and vapply()
    that can be resolved using any future-supported backend, e.g.
    parallel on the local machine or distributed on a compute cluster.
    These future_*apply() functions come with the same pros and cons
    as the corresponding base-R *apply() functions but with the additional
    feature of being able to be processed via the future framework.
    
    WWW: https://cran.r-project.org/web/packages/future.apply/
---
 devel/Makefile                      |  1 +
 devel/R-cran-future.apply/Makefile  | 18 ++++++++++++++++++
 devel/R-cran-future.apply/distinfo  |  3 +++
 devel/R-cran-future.apply/pkg-descr |  9 +++++++++
 4 files changed, 31 insertions(+)

diff --git a/devel/Makefile b/devel/Makefile
index 829667822579..da32000c64b2 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -43,6 +43,7 @@
     SUBDIR += R-cran-filelock
     SUBDIR += R-cran-foreach
     SUBDIR += R-cran-future
+    SUBDIR += R-cran-future.apply
     SUBDIR += R-cran-gbRd
     SUBDIR += R-cran-gbm
     SUBDIR += R-cran-gdata
diff --git a/devel/R-cran-future.apply/Makefile b/devel/R-cran-future.apply/Makefile
new file mode 100644
index 000000000000..b2826ff9a040
--- /dev/null
+++ b/devel/R-cran-future.apply/Makefile
@@ -0,0 +1,18 @@
+PORTNAME=	future.apply
+PORTVERSION=	1.8.1
+CATEGORIES=	devel
+DISTNAME=	${PORTNAME}_${PORTVERSION}
+
+MAINTAINER=	tota at FreeBSD.org
+COMMENT=	Apply Function to Elements in Parallel using Futures
+
+LICENSE=	GPLv2+
+
+CRAN_DEPENDS=	R-cran-future>=1.21.0:devel/R-cran-future \
+		R-cran-globals>=0.14.0:devel/R-cran-globals
+BUILD_DEPENDS=	${CRAN_DEPENDS}
+RUN_DEPENDS=	${CRAN_DEPENDS}
+
+USES=		cran:auto-plist
+
+.include <bsd.port.mk>
diff --git a/devel/R-cran-future.apply/distinfo b/devel/R-cran-future.apply/distinfo
new file mode 100644
index 000000000000..dc6a381a06c2
--- /dev/null
+++ b/devel/R-cran-future.apply/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1631099037
+SHA256 (future.apply_1.8.1.tar.gz) = 0d5bc3cb0289665bb27ae4ccad51fcc5ebf6dca46872b0a4e57790b9dc0aa6c7
+SIZE (future.apply_1.8.1.tar.gz) = 63654
diff --git a/devel/R-cran-future.apply/pkg-descr b/devel/R-cran-future.apply/pkg-descr
new file mode 100644
index 000000000000..47740564d7df
--- /dev/null
+++ b/devel/R-cran-future.apply/pkg-descr
@@ -0,0 +1,9 @@
+Implementations of apply(), by(), eapply(), lapply(), Map(),
+.mapply(), mapply(), replicate(), sapply(), tapply(), and vapply()
+that can be resolved using any future-supported backend, e.g.
+parallel on the local machine or distributed on a compute cluster.
+These future_*apply() functions come with the same pros and cons
+as the corresponding base-R *apply() functions but with the additional
+feature of being able to be processed via the future framework.
+
+WWW: https://cran.r-project.org/web/packages/future.apply/