Arch Linux User Repository

A note for users.

This package is quite complex. It MAY not be built because of OTHER issues. I always build, install and test it on at least two different machines. Only after that I would push a new version to AUR.

Please try some generic solutions before reporting of build problems:

1) Update all other packages (sudo pacman -Syu),

2) Clean up yay and/or makepkg caches ('yay -Sc', 'rm -rf /var/tmp/makepkg'),

3) Be sure you've got enough RAM (8 GB or more is highly recommended) and space on disk (at least 3 GB).

4) Is your Internet connection is stable, fast and not blocked somewhere?

PLEASE READ THIS MESSAGE BEFORE COMPLAINING FOR LIBBOOST

When boost is updated to a new version and you see an error message about missing libboost*.so, you will need to rebuild and reinstall the rstudio-desktop package.

Build logic is slightly changed due to changes in upstream. As they've introduced new project format (quarto), it contradicted with standard Arch package base. In brief, quarto contains pandoc as part of itself, so it's pretty hard to keep together system pandoc and embedded quarto.

So I've "resolved" it such way: if there is "quarto*" package installed, then rstudio-desktop will pick it up and use. Otherwise (not installed), quarto support in rstudio will be disabled.

'quarto' is added as optional dependency.

Hi @kbipinkumar,

rstudio devs have started advising rstudio to be built with electron

Well. As far as I can see it's related to development branch at the moment. Stable releases still support 'Desktop' target (as well as all Docker configurations). If/When they announce such deprecation for the next release, I'll either switch to electron or give up and relax of this package maintaining.

Meanwhile you can experiment with electron version - there is an dev AUR package rstudio-desktop-git - either contact maintainer or adopt.

UPD: Electron is insane. I've just built a test package: archive size is 100M vs 20M (315M vs 90M on disk installed)

-rw-r--r-- 1 trap000d trap000d  20M Aug 24 15:44 rstudio-desktop-2023.06.2.561-1-x86_64.pkg.tar.zst
-rw-r--r-- 1 trap000d trap000d 105M Aug 28 09:37 rstudio-desktop-2023.06.2.561-2-x86_64.pkg.tar.zst

@kbipinkumar Shouldn't that be a separate package, rstudio-electron? Or even just rstudio?

rstudio devs have started advising rstudio to be built with electron

Note, the target "Electron" should be used when building the Desktop IDE.
The "Desktop" target builds the legacy Qt application, is no longer 
supported, and will eventually be removed.

any update on PKGBUILD being updated to reflect the same?

I don't use this package. It builds on a server, and someone else noticed it doesn't work with quarto. So I'm trying to "fix" the package on the server. If it's too complicated, I'll just leave it alone.

Yes, if it was built without quarto, it couldn't recognize quarto projects.

If the package is built with quarto-cli-bin quarto still optional, or does it become a runtime dependency?

In short, if quarto is detected at configuration time, several extra menus, options and dialogs are added to RStudio binary. Runtime dependency is still optional: you can remove quarto package after, however RStudio will run OK. User may have got an error message in R console if try to open and render quarto project, though.

I don't use this package. It builds on a server, and someone else noticed it doesn't work with quarto. So I'm trying to "fix" the package on the server. If it's too complicated, I'll just leave it alone.

If the package is built with quarto-cli-bin is quarto still optional, or does it become a runtime dependency?

Is it possible to build the quarto modules separately, as an addon package??

Is there a way to "support" quarto without having to build this package with it?

I afraid, no. Quarto must be explicitly included or excluded at configuration time. If you include it, quarto will be called to create several internal RStudio modules and libraries during the build process.

I thought a bit of forking rstudio-desktop to e.g. rstudio-desktop-full and rstudio-desktop-no-quarto, but ended up with current "solution".

At least I can see some logic here: configure => check module => available => include it : not available => not include.

P.S. If you believe you can make it better, you're welcome to adopt this package (but don't forget to take quarto-cli, quarto-cli-pre-release and quarto-cli-git as well)

:)

Didn't realize I was stumbling into a years-old issue... Is there a way to "support" quarto without having to build this package with it?

When using a clean chroot, quarto is not installed while building this package. From what I can tell, the resulting package will not support quarto, even when quarto is installed. If this is the case, should quarto be added to makedepends?

@xiota, this is kind of issue with no good solution. Quarto itself is not an example of solid and stable software. Some users do not want to build RStudio with it due to dependency problems.

On the other hand there are people who are not happy with binary Quarto package (quarto-bin). At the moment Quarto doesn't build with esbuild>=0.18 (I had to roll back esbuild to 0.17 in dependencies of quarto-cli-pre-release until they fix the issue in upstream).

If I add quarto as makedepends, building of RStudio will become much harder than now.

After some discussion here few years ago I ended up with adding quarto as optional dependency.

As an override you might build or download quarto package and then feed the chroot with it:

CHROOT=$HOME/src/chroot
QUARTO_PKG=quarto-cli-pre-release-1.4.161-1-x86_64.pkg.tar.zst
makechrootpkg -c -r $CHROOT -I $QUARTO_PKG

When using a clean chroot, quarto is not installed while building this package. From what I can tell, the resulting package will not support quarto, even when quarto is installed. If this is the case, should quarto be added to makedepends?

@nunonun, yep, that's kind of known "feauture" of github. Fixed by skipping of archive checksum.