git: c710d1b797a5 - main - textproc/R-cran-R.rsp: New port

The branch main has been updated by uzsolt:

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

commit c710d1b797a53262b90e05d60f5aa73c4e1bac32
Author:     Zsolt Udvari <uzsolt@FreeBSD.org>
AuthorDate: 2025-02-16 18:17:13 +0000
Commit:     Zsolt Udvari <uzsolt@FreeBSD.org>
CommitDate: 2025-02-16 18:18:33 +0000

    textproc/R-cran-R.rsp: New port
    
    The RSP markup language makes any text-based document come alive. RSP provides a
    powerful markup for controlling the content and output of LaTeX, HTML, Markdown,
    AsciiDoc, Sweave and knitr documents (and more), e.g. 'Today's date is
    <%=Sys.Date()%>'. Contrary to many other literate programming languages, with
    RSP it is straightforward to loop over mixtures of code and text sections, e.g.
    in month-by-month summaries. RSP has also several preprocessing directives for
    incorporating static and dynamic contents of external files (local or online)
    among other things. Functions rstring() and rcat() make it easy to process RSP
    strings, rsource() sources an RSP file as it was an R script, while rfile()
    compiles it (even online) into its final output format, e.g.
    rfile('report.tex.rsp') generates 'report.pdf' and rfile('report.md.rsp')
    generates 'report.html'. RSP is ideal for self-contained scientific reports and
    R package vignettes. It's easy to use - if you know how to write an R script,
    you'll be up and running within minutes.
---
 textproc/Makefile               |  1 +
 textproc/R-cran-R.rsp/Makefile  | 27 +++++++++++++++++++++++++++
 textproc/R-cran-R.rsp/distinfo  |  3 +++
 textproc/R-cran-R.rsp/pkg-descr | 14 ++++++++++++++
 4 files changed, 45 insertions(+)

diff --git a/textproc/Makefile b/textproc/Makefile
index 054824b581bf..49e0b0914511 100644
--- a/textproc/Makefile
+++ b/textproc/Makefile
@@ -3,6 +3,7 @@
     SUBDIR += 2bsd-diff
     SUBDIR += CLDR
     SUBDIR += R-cran-DT
+    SUBDIR += R-cran-R.rsp
     SUBDIR += R-cran-R2HTML
     SUBDIR += R-cran-XML
     SUBDIR += R-cran-bibtex
diff --git a/textproc/R-cran-R.rsp/Makefile b/textproc/R-cran-R.rsp/Makefile
new file mode 100644
index 000000000000..4df7ef39d548
--- /dev/null
+++ b/textproc/R-cran-R.rsp/Makefile
@@ -0,0 +1,27 @@
+PORTNAME=	R.rsp
+DISTVERSION=	0.46.0
+CATEGORIES=	textproc
+DISTNAME=	${PORTNAME}_${PORTVERSION}
+
+MAINTAINER=	uzsolt@FreeBSD.org
+COMMENT=	Dynamic Generation of Scientific Reports
+WWW=		https://cran.r-project.org/package=R.rsp
+
+LICENSE=	LGPL21 LGPL3
+LICENSE_COMB=	multi
+
+RUN_DEPENDS=	R-cran-digest>0:security/R-cran-digest \
+		R-cran-R.cache>0:devel/R-cran-R.cache \
+		R-cran-R.methodsS3>=1.8.0:devel/R-cran-R.methodsS3 \
+		R-cran-R.oo>=1.23.0:devel/R-cran-R.oo \
+		R-cran-R.utils>0:devel/R-cran-R.utils
+TEST_DEPENDS=	R-cran-base64enc>0:converters/R-cran-base64enc \
+		R-cran-knitr>0:print/R-cran-knitr \
+		R-cran-markdown>0:textproc/R-cran-markdown \
+		R-cran-R.devices>0:graphics/R-cran-R.devices
+
+USES=		cran:auto-plist shebangfix
+
+SHEBANG_FILES=	inst/tcl/r-httpd.tcl
+
+.include <bsd.port.mk>
diff --git a/textproc/R-cran-R.rsp/distinfo b/textproc/R-cran-R.rsp/distinfo
new file mode 100644
index 000000000000..b4458c3c0a56
--- /dev/null
+++ b/textproc/R-cran-R.rsp/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1739691214
+SHA256 (R.rsp_0.46.0.tar.gz) = 1a9f680ffe563abdaa91add6ebf5e6c0ecbe57f0d39687bcb272ff2a987c33bb
+SIZE (R.rsp_0.46.0.tar.gz) = 680925
diff --git a/textproc/R-cran-R.rsp/pkg-descr b/textproc/R-cran-R.rsp/pkg-descr
new file mode 100644
index 000000000000..d7e79a4407e9
--- /dev/null
+++ b/textproc/R-cran-R.rsp/pkg-descr
@@ -0,0 +1,14 @@
+The RSP markup language makes any text-based document come alive. RSP provides a
+powerful markup for controlling the content and output of LaTeX, HTML, Markdown,
+AsciiDoc, Sweave and knitr documents (and more), e.g. 'Today's date is
+<%=Sys.Date()%>'. Contrary to many other literate programming languages, with
+RSP it is straightforward to loop over mixtures of code and text sections, e.g.
+in month-by-month summaries. RSP has also several preprocessing directives for
+incorporating static and dynamic contents of external files (local or online)
+among other things. Functions rstring() and rcat() make it easy to process RSP
+strings, rsource() sources an RSP file as it was an R script, while rfile()
+compiles it (even online) into its final output format, e.g.
+rfile('report.tex.rsp') generates 'report.pdf' and rfile('report.md.rsp')
+generates 'report.html'. RSP is ideal for self-contained scientific reports and
+R package vignettes. It's easy to use - if you know how to write an R script,
+you'll be up and running within minutes.