CRAN Package Check Results for Package BrailleR

Last updated on 2025-05-02 04:49:30 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.0.2 15.43 257.35 272.78 NOTE
r-devel-linux-x86_64-debian-gcc 1.0.2 12.38 179.08 191.46 NOTE
r-devel-linux-x86_64-fedora-clang 1.0.2 432.91 NOTE
r-devel-linux-x86_64-fedora-gcc 1.0.2 460.99 NOTE
r-devel-windows-x86_64 1.0.2 20.00 295.00 315.00 NOTE
r-patched-linux-x86_64 1.0.2 16.03 246.84 262.87 NOTE
r-release-linux-x86_64 NOTE
r-release-macos-arm64 1.0.2 121.00 NOTE
r-release-macos-x86_64 1.0.2 222.00 NOTE
r-release-windows-x86_64 1.0.2 22.00 278.00 300.00 NOTE
r-oldrel-macos-arm64 1.0.2 115.00 OK
r-oldrel-macos-x86_64 1.0.2 187.00 OK
r-oldrel-windows-x86_64 1.0.2 25.00 334.00 359.00 OK

Check Details

Version: 1.0.2
Check: DESCRIPTION meta-information
Result: NOTE Missing dependency on R >= 4.2.0 because package code uses the pipe placeholder syntax added in R 4.2.0. File(s) using such syntax: ‘AddXMLInternal.R’ ‘BrowseSVG.R’ ‘MakeAccessibleSVGInternal.R’ ‘RewriteSVG.R’ ‘ViewSVG.R’ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-windows-x86_64

Version: 1.0.2
Check: examples
Result: NOTE Examples with CPU (user + system) or elapsed time > 5s user system elapsed MakeAccessibleSVGMethod 7.099 0.065 9.384 ViewSVG 6.801 0.007 8.570 TwoFactors 4.904 0.020 7.613 OneFactor 3.760 0.139 5.201 Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.0.2
Check: DESCRIPTION meta-information
Result: NOTE Missing dependency on R >= 4.1.0 because package code uses the pipe |> or function shorthand \(...) syntax added in R 4.1.0. File(s) using such syntax: ‘AddXMLInternal.R’ ‘BrowseSVG.R’ ‘Describe.R’ ‘MakeAccessibleSVGInternal.R’ ‘RewriteSVG.R’ ‘VIInternals.R’ ‘VIMethod3_TH.R’ ‘ViewSVG.R’ Flavor: r-release-macos-x86_64

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.