%global __brp_check_rpaths %{nil}
%global __requires_exclude ^libmpi
%global packname  shinylive
%global packver   0.3.0
%global rlibdir   /usr/local/lib/R/library

Name:             R-CRAN-%{packname}
Version:          0.3.0
Release:          1%{?dist}%{?buildtag}
Summary:          Run 'shiny' Applications in the Browser

License:          MIT + file LICENSE
URL:              https://cran.r-project.org/package=%{packname}
Source0:          %{url}&version=%{packver}#/%{packname}_%{packver}.tar.gz


BuildRequires:    R-devel
Requires:         R-core
BuildArch:        noarch
BuildRequires:    R-CRAN-httr2 >= 1.0.0
BuildRequires:    R-CRAN-archive 
BuildRequires:    R-CRAN-brio 
BuildRequires:    R-CRAN-cli 
BuildRequires:    R-CRAN-fs 
BuildRequires:    R-CRAN-gh 
BuildRequires:    R-CRAN-glue 
BuildRequires:    R-CRAN-jsonlite 
BuildRequires:    R-CRAN-pkgdepends 
BuildRequires:    R-CRAN-progress 
BuildRequires:    R-CRAN-rappdirs 
BuildRequires:    R-CRAN-renv 
BuildRequires:    R-CRAN-rlang 
BuildRequires:    R-tools 
BuildRequires:    R-CRAN-whisker 
BuildRequires:    R-CRAN-withr 
Requires:         R-CRAN-httr2 >= 1.0.0
Requires:         R-CRAN-archive 
Requires:         R-CRAN-brio 
Requires:         R-CRAN-cli 
Requires:         R-CRAN-fs 
Requires:         R-CRAN-gh 
Requires:         R-CRAN-glue 
Requires:         R-CRAN-jsonlite 
Requires:         R-CRAN-pkgdepends 
Requires:         R-CRAN-progress 
Requires:         R-CRAN-rappdirs 
Requires:         R-CRAN-renv 
Requires:         R-CRAN-rlang 
Requires:         R-tools 
Requires:         R-CRAN-whisker 
Requires:         R-CRAN-withr 

%description
Exporting 'shiny' applications with 'shinylive' allows you to run them
entirely in a web browser, without the need for a separate R server. The
traditional way of deploying 'shiny' applications involves in a separate
server and client: the server runs R and 'shiny', and clients connect via
the web browser. When an application is deployed with 'shinylive', R and
'shiny' run in the web browser (via 'webR'): the browser is effectively
both the client and server for the application. This allows for your
'shiny' application exported by 'shinylive' to be hosted by a static web
server.

%prep
%setup -q -c -n %{packname}

# fix end of executable files
find -type f -executable -exec grep -Iq . {} \; -exec sed -i -e '$a\' {} \;
# prevent binary stripping
[ -d %{packname}/src ] && find %{packname}/src -type f -exec \
  sed -i 's@/usr/bin/strip@/usr/bin/true@g' {} \; || true
[ -d %{packname}/src ] && find %{packname}/src/Make* -type f -exec \
  sed -i 's@-g0@@g' {} \; || true
# don't allow local prefix in executable scripts
find -type f -executable -exec sed -Ei 's@#!( )*/usr/local/bin@#!/usr/bin@g' {} \;

%build

%install

mkdir -p %{buildroot}%{rlibdir}
%{_bindir}/R CMD INSTALL -l %{buildroot}%{rlibdir} %{packname}
test -d %{packname}/src && (cd %{packname}/src; rm -f *.o *.so)
rm -f %{buildroot}%{rlibdir}/R.css
# remove buildroot from installed files
find %{buildroot}%{rlibdir} -type f -exec sed -i "s@%{buildroot}@@g" {} \;

%files
%{rlibdir}/%{packname}