5 Commits

Include renames

Author	SHA1	Message	Date
agw	7dd99f0b7d	Actually ship the R libraries the modules need ... The first full build succeeded and produced a package that would not have worked. Three separate causes, all silent: - R was configured --with-blas --with-lapack, so it linked Arch's external BLAS and never built libRblas.so/libRlapack.so. The JASP module bundles expect those inside R_HOME, the way a conventional R and the Flatpak ship them. Now --without-blas, with a hard check after install. - buildModuleBundlesLocally.R installs jaspModuleTools via install_github, which failed on anonymous GitHub rate limits. No bundles were produced at all. GITHUB_PAT is now required rather than merely recommended. - buildAllDefaultJaspModules.R calls the bundle builder through system2(), which ignores exit status, so all of the above exited 0. Added explicit guards: jaspModuleTools must exist, Modules/local must be non-empty, and the staged tree must contain the bundles and all three R libraries. Staging was also wrong: it copied ModuleBundleBuildDir/Modules, which is cloned module *sources* with zero compiled objects, while dropping LibraryR entirely - 267MB of R packages built against the bundled R.	2026-09-01 23:30:00 +02:00
agw	56434ba7ed	Bundle non-system libraries instead of version-pinning depends ... Bundling R alone was not enough: R links libicuuc, and Arch moves ICU regularly. The obvious fix - pinning 'icu>=78 <79' in depends - is worse than the disease on a rolling distro, because pacman would then refuse to upgrade ICU while JASP is installed, blocking the user's whole system upgrade until a rebuild lands. So bundle-libs.sh copies every non-system shared library into /opt/jasp-desktop/lib and rewrites rpaths, by denylist rather than allowlist. depends now carries no version constraints at all. Qt6 stays system-provided on purpose - Qt is binary compatible across Qt 6 minors, and bundling QtWebEngine would add ~500 MB. That also means the only rebuild triggers left are a new JASP release and a Qt major bump; rebuilding for anything else would cost users a 1.7 GB re-download. Also fixes check-upstream.py querying only repo=Extra, which silently returned nothing for icu (it lives in core).	2026-09-01 22:05:00 +02:00
agw	7b39a5b06e	Fix R bundling: SIGPIPE abort and wrong R_HOME path ... Two bugs found by the first real build: - 'R --version | head -1' aborted the script with exit 141 under 'set -o pipefail': head closes the pipe and R dies of SIGPIPE. Use 'sed -n 1p', which consumes all input. - R installed to lib64/R, not the lib/R the script assumed. Pin --libdir and ask 'R RHOME' for the real path instead of guessing. Also stop exporting R_HOME. R.cmake warns that a set R_HOME makes R emit 'WARNING: ignoring environment value of R_HOME', which corrupts the output cmake parses; CUSTOM_R_PATH is the supported way to select an R.	2026-09-01 21:55:00 +02:00
agw	d880e6748c	Bundle our own R 4.5.3 instead of building against Arch's R ... Arch ships R 4.6.1, but JASP pins its R packages against a frozen CRAN snapshot (2026-03-31 for 0.98.1) that targets R 4.5. Configuring against Arch's R fails at Rcpp 1.1.1, which cannot compile on R 4.6 since R_NamespaceRegistry was removed; the Rcpp release that fixes it is newer than the pinned snapshot, so the lockfile cannot reach it either. Build R 4.5.3 into /opt/jasp-desktop/R and point R_HOME at it, matching what upstream CI does. This drops 'r' from depends entirely, so an Arch R upgrade can no longer break an installed JASP, and the rebuild triggers become Qt6 and ICU - the libraries actually still linked against.	2026-09-01 21:40:00 +02:00
agw	0d4db32d5c	Automated Arch binary builds of JASP for the AUR ... Upstream JASP ships no Linux binary, so the existing AUR package builds everything from source including several hundred R packages. This builds that once in CI and publishes the result as jasp-desktop-bin. JASP links against the system R and Qt6 rather than bundling them, so a rebuild is triggered by an Arch r/qt6-base bump as well as by a new JASP release, and the generated PKGBUILD pins depends to the versions actually built against.	2026-09-01 20:30:00 +02:00