Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Sep 2021 13:02:17 GMT
From:      TAKATSU Tomonari <tota@FreeBSD.org>
To:        ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org
Subject:   git: 4f10a7557af6 - main - devel/R-cran-progressr: Add new port
Message-ID:  <202109071302.187D2HR3066765@gitrepo.freebsd.org>

next in thread | raw e-mail | index | archive | help
The branch main has been updated by tota:

URL: https://cgit.FreeBSD.org/ports/commit/?id=4f10a7557af62fdf756dc5f4290e83249f4979ff

commit 4f10a7557af62fdf756dc5f4290e83249f4979ff
Author:     TAKATSU Tomonari <tota@FreeBSD.org>
AuthorDate: 2021-09-07 12:53:30 +0000
Commit:     TAKATSU Tomonari <tota@FreeBSD.org>
CommitDate: 2021-09-07 12:53:30 +0000

    devel/R-cran-progressr: Add new port
    
    A minimal, unifying API for scripts and packages to report progress
    updates from anywhere including when using parallel processing. The
    package is designed such that the developer can to focus on what
    progress should be reported on without having to worry about how
    to present it. The end user has full control of how, where, and
    when to render these progress updates, e.g. in the terminal using
    utils::txtProgressBar() or progress::progress_bar(), in a graphical
    user interface using utils::winProgressBar(), tcltk::tkProgressBar()
    or shiny::withProgress(), via the speakers using beep::beepr(), or
    on a file system via the size of a file. Anyone can add additional,
    customized, progression handlers. The 'progressr' package uses R's
    condition framework for signaling progress updated. Because of this,
    progress can be reported from almost anywhere in R, e.g. from
    classical for and while loops, from map-reduce APIs like the lapply()
    family of functions, 'purrr', 'plyr', and 'foreach'. It will also
    work with parallel processing via the 'future' framework, e.g.
    future.apply::future_lapply(), furrr::future_map(), and 'foreach'
    with 'doFuture'. The package is compatible with Shiny applications.
    
    WWW: https://cran.r-project.org/web/packages/progressr/
---
 devel/Makefile                   |  1 +
 devel/R-cran-progressr/Makefile  | 17 +++++++++++++++++
 devel/R-cran-progressr/distinfo  |  3 +++
 devel/R-cran-progressr/pkg-descr | 20 ++++++++++++++++++++
 4 files changed, 41 insertions(+)

diff --git a/devel/Makefile b/devel/Makefile
index dd4a073f2c39..20d1f3f014a7 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -78,6 +78,7 @@
     SUBDIR += R-cran-prettycode
     SUBDIR += R-cran-prettyunits
     SUBDIR += R-cran-progress
+    SUBDIR += R-cran-progressr
     SUBDIR += R-cran-promises
     SUBDIR += R-cran-proto
     SUBDIR += R-cran-purrr
diff --git a/devel/R-cran-progressr/Makefile b/devel/R-cran-progressr/Makefile
new file mode 100644
index 000000000000..40b552dddf60
--- /dev/null
+++ b/devel/R-cran-progressr/Makefile
@@ -0,0 +1,17 @@
+PORTNAME=	progressr
+PORTVERSION=	0.8.0
+CATEGORIES=	devel
+DISTNAME=	${PORTNAME}_${PORTVERSION}
+
+MAINTAINER=	tota@FreeBSD.org
+COMMENT=	Inclusive, Unifying API for Progress Updates
+
+LICENSE=	GPLv3
+
+CRAN_DEPENDS=	R-cran-digest>0:security/R-cran-digest
+BUILD_DEPENDS=	${CRAN_DEPENDS}
+RUN_DEPENDS=	${CRAN_DEPENDS}
+
+USES=		cran:auto-plist
+
+.include <bsd.port.mk>
diff --git a/devel/R-cran-progressr/distinfo b/devel/R-cran-progressr/distinfo
new file mode 100644
index 000000000000..372bf14d6879
--- /dev/null
+++ b/devel/R-cran-progressr/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1631017849
+SHA256 (progressr_0.8.0.tar.gz) = 8224d397cea450d97a08ed94ecc76f6e46fd46faa89882834e71b654ba07f7d4
+SIZE (progressr_0.8.0.tar.gz) = 105785
diff --git a/devel/R-cran-progressr/pkg-descr b/devel/R-cran-progressr/pkg-descr
new file mode 100644
index 000000000000..5fca3ffd89c9
--- /dev/null
+++ b/devel/R-cran-progressr/pkg-descr
@@ -0,0 +1,20 @@
+A minimal, unifying API for scripts and packages to report progress
+updates from anywhere including when using parallel processing. The
+package is designed such that the developer can to focus on what
+progress should be reported on without having to worry about how
+to present it. The end user has full control of how, where, and
+when to render these progress updates, e.g. in the terminal using
+utils::txtProgressBar() or progress::progress_bar(), in a graphical
+user interface using utils::winProgressBar(), tcltk::tkProgressBar()
+or shiny::withProgress(), via the speakers using beep::beepr(), or
+on a file system via the size of a file. Anyone can add additional,
+customized, progression handlers. The 'progressr' package uses R's
+condition framework for signaling progress updated. Because of this,
+progress can be reported from almost anywhere in R, e.g. from
+classical for and while loops, from map-reduce APIs like the lapply()
+family of functions, 'purrr', 'plyr', and 'foreach'. It will also
+work with parallel processing via the 'future' framework, e.g.
+future.apply::future_lapply(), furrr::future_map(), and 'foreach'
+with 'doFuture'. The package is compatible with Shiny applications.
+
+WWW: https://cran.r-project.org/web/packages/progressr/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202109071302.187D2HR3066765>