Package Details: rstudio-desktop 2024.12.0.467-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.027668
First Submitted: 2011-03-04 15:02 (UTC)
Last Updated: 2024-12-20 21:33 (UTC)

Dependencies (29)

Required by (0)

Sources (3)

Pinned Comments

trap000d commented on 2024-05-16 21:42 (UTC) (edited on 2024-05-28 20:09 (UTC) by trap000d)

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?

trap000d commented on 2022-07-05 20:32 (UTC) (edited on 2022-10-03 06:28 (UTC) by trap000d)

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.

trap000d commented on 2022-02-19 06:20 (UTC) (edited on 2022-02-19 06:21 (UTC) by trap000d)

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.

Latest Comments

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 Next › Last »

td123 commented on 2011-03-20 03:45 (UTC)

jowilkin, another solution to the missing apache and problem is to do the following line in the PKGBUILD: source /etc/profile.d/apache-ant.sh

<deleted-account> commented on 2011-03-20 00:52 (UTC)

jelly - GWT is in AUR, but the RStudio build process expects it to be in a very specific place (the place that the build process downloads it to). I've contacted the devs to see if it's possible to use an existing installation of GWT instead, but in it's current state, it won't build unless the GWT installation is present in the source tree. The boost errors are also fixed in the RStudio git tree, so there are no errors building the git package right now related to boost. If this package does currently have errors related to boost requiring modification of the compile flags, then that will be fixed by updating to a newer tag in the RStudio git repo. zeltak - that most likely means that you had apache-ant installed as a dependency during the build process. You need to log out and log back in so that ant is placed on your PATH, and then the build should work for you. It's a limitation of the way ant is packaged that it will not appear on your PATH after you install it unless you log out and back in.

<deleted-account> commented on 2011-03-18 15:05 (UTC)

Hi zeltak, this may be because you don't have java or ANT installed or configured on the system correctly - the script used to sort this but it was changed to just give an error, because it went and altered a persons files ad made an unmanaged link so was deemed bad practice, and so I implemented a method suggested by jwolkin below in his git version of this package. I'm not 100 % sure on what a person should do if this is indeed the cause of the error - myself I used the PKGBUILD back when it created the link so all other versions up to now work for my machine - which makes it difficult to determine if others will have issues. If this is indeed the source of the error I think what you need to do is make sure ant is on the PATH. If it is not the error then I'm unsure - it's a completely new one to me. There is a forum thread here https://bbs.archlinux.org/viewtopic.php?id=114333&p=3 which has discussion of building r-studio. An alternative would be to set up a github account and see if the git version does the same thing.

zeltak commented on 2011-03-16 16:16 (UTC)

Hi im a neewb trying to install r-studio. i get this error : -> Extracting v0.93.35 with bsdtar ==> Starting build()... which: no ant in (/home/zeltak/bin/scrot:/home/zeltak/bin:/home/zeltak/bin/scrot:/home/zeltak/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/lib/perl5/site_perl/bin:/usr/bin/vendor_perl:/usr/lib/perl5/vendor_perl/bin:/usr/bin/core_perl) Aborting... The build failed is there someway to fix it? thx Z.

jelly commented on 2011-03-15 11:12 (UTC)

export CXXFLAGS="${CXXFLAGS} -DBOOST_FILESYSTEM_VERSION=2" before ./configure, to fix the boost errors

jelly commented on 2011-03-15 11:01 (UTC)

did you notice GWT is in AUR?

<deleted-account> commented on 2011-03-14 21:07 (UTC)

I was working on a way to check for ant and java and the method reztho is what first occurred to me, but it doesn't quite work as expected since makepkg will now exit immediately upon an error. So if we test the exit code for an error and then output a message, makepkg will exit immediately upon the error and the message will never get printed. This is the compromise I think works well: # Check if ant and java can be found msg "Checking if java and ant are on the PATH...." which ant > /dev/null which java > /dev/null This will output nothing if ant and java are found (stdout goes to /dev/null), but if they are not found an error message will be printed by "which" to stderr and then makepkg will exit as a result of which not returning 0.

<deleted-account> commented on 2011-03-14 19:42 (UTC)

The ant link was my fault :P It was a hack to get it working the first time, but I did not include it in my rstudio git pkbuild, I should have noted on the forum that it was a bad idea. The warning is a much more sane way to handle this, I only have a note in the comments of the git pkgbuild.

<deleted-account> commented on 2011-03-10 20:24 (UTC)

Thanks reztho, I've altered it and it'll be uploaded later when it's no longer peak time here. I did wonder about it, because it was included in the forum dedicated to this, but when I built the package manually first hand from source, the first time it worked I didn't do anything about ant.

reztho commented on 2011-03-10 17:21 (UTC)

# link apache ant? if [ ! -e /usr/bin/ant ] ; then msg "Creating a link so that make can find apache ant" ln -s /usr/share/java/apache-ant/bin/ant /usr/bin/ant fi For god's sake, do not do that. Makepkg isn't supposed to be run under a root account. And those people who do it are going to have an unmanaged symbolic link by pacman which can make problems in the future. Instead just check ant is accesible and if it's not, throw a warning message to the user if you want to and exit gracefully. Something like this should work: which ant &> /dev/null if [ $? -gt 0 ]; then msg "whatever" exit 1 fi Apache-ant package comes with a bash script (/etc/profile.d/apache-ant.sh) which needs to be sourced before doing anything the first time is installed or the user just needs to relogin for it being sourced automatically. Makepkg just fakes root perms; it doesn't make a chroot. AUR isn't supposed to be user friendly and it's your responsibility not to mess with people's filesystem, that's why there aren't any AUR helper in community.