Package Details: rstudio-desktop 2025.05.0.496-1

Git Clone URL: https://aur.archlinux.org/rstudio-desktop.git (read-only, click to copy)
Package Base: rstudio-desktop
Description: A powerful and productive integrated development environment (IDE) for R programming language
Upstream URL: https://github.com/rstudio/rstudio
Licenses: AGPL-3.0-only
Conflicts: rstudio-desktop
Provides: rstudio-desktop
Submitter: None
Maintainer: xiota
Last Packager: xiota
Votes: 73
Popularity: 0.42
First Submitted: 2011-03-04 15:02 (UTC)
Last Updated: 2025-05-12 06:23 (UTC)

Dependencies (36)

Required by (0)

Sources (4)

Pinned Comments

xiota commented on 2025-03-01 05:16 (UTC) (edited on 2025-05-01 20:46 (UTC) by xiota)

Packaging notes:

  • Given the inconvenience of having this package become unusable for an indefinite amount time, sodeps are used to prevent boost upgrades from breaking this package. Others may be added. Updates may need to be forced with pacman -Syudd prior to rebuilding. This is unnecessary when building in a clean chroot.
  • Any variable declared : ${var:=value} can be set in the environment prior to build.
    • For example: var=value makepkg -rsC; Method for AUR helpers may vary.
    • For clean chroot, try something like: extra-x86_64-build -- var=value

Problems?

  • Try building in a clean chroot.
  • If your distro has delayed updates, you may need to wait a few weeks.
  • Avoid commenting and flagging for the same issue at the same time.
    • Flag for routine and mechanical issues (depends, typos, mistakes, etc)
    • Comment for issues requiring discussion.
    • Please use a pastebin for blocks of text more than a few lines.

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 31 Next › Last »

trap000d commented on 2023-08-28 00:25 (UTC)

@xiota,

Basically, I don't mind to pass the maintenance of rstudio-desktop to somebody else (but only with all those quarto-cli*, which I have to keep too, and which actually take more efforts from me than rstudio).

As for proposed changes. Do you have a corresponding PKGBUILD on a hand so I could take a look an test it?

Basically, I've got the following concerns.

It's a bit unclear to me, how would conflicts with various rstudio-desktop* builds be resolved with provides= only.

According to official Arch documentation, "Packages providing the same item can be installed side-by-side, unless at least one of them uses a conflicts array."

As for quarto - there are several quarto-cli* builds available at AUR. How you're going to choose a particular one?

Also, AUR guidelines make it quite clear - one shouldn't use any third party binaries in source packages:

"Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix."

So if you add quarto-cli-bin as non-alternative dependency, that will switch the main package name to -bin. But rstudio-desktop-bin is exists and maintained: releases appear up-to-date.

trap000d commented on 2023-08-27 21:38 (UTC) (edited on 2023-08-27 21:47 (UTC) by trap000d)

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

xiota commented on 2023-08-27 21:32 (UTC) (edited on 2023-08-27 21:32 (UTC) by xiota)

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

kbipinkumar commented on 2023-08-27 18:40 (UTC)

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?

trap000d commented on 2023-06-22 22:32 (UTC) 

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.

xiota commented on 2023-06-22 01:24 (UTC) (edited on 2023-06-22 01:26 (UTC) by xiota)

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??

trap000d commented on 2023-06-22 01:03 (UTC) 

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)

:)

xiota commented on 2023-06-22 00:31 (UTC)

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?

trap000d commented on 2023-06-21 08:49 (UTC) (edited on 2023-06-21 08:50 (UTC) by trap000d)

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

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 31 Next › Last »