Package Details: rstudio-desktop-git 1.2.5033.r5032-1

Git Clone URL: https://aur.archlinux.org/rstudio-desktop-git.git (read-only, click to copy) rstudio-desktop-git A powerful and productive integrated development environment (IDE) for R programming language https://www.rstudio.com/products/rstudio/ ide r rstudio AGPL3 rstudio-desktop, rstudio-desktop-bin, rstudio-desktop-preview rstudio-desktop None artemklevtsov (hwkiller, ConorIA, kngwyu) artemklevtsov 58 1.24 2011-03-09 06:13 2020-05-10 08:00

Sources (7)

artemklevtsov commented on 2020-04-10 02:30

I created repo on GitLab to automate daily builds. PRs are welcome.

Repo entry for the pacman.conf:

[rstudio]
SigLevel = PackageOptional
Server = https://aur1.gitlab.io/$repo/$arch


Packages:

icu60
microsoft-r-open
ncurses5-compat-libs
pandoc-bin
r-devel
r-mkl
rstudio-desktop
rstudio-desktop-git
rstudio-server-git
soci


Source code: https://gitlab.com/aur1/rstudio

Atraii commented on 2017-09-28 22:25

rkelly: You'll need to recompile and reinstall this package against the new boost libraries. I have this issue as well AND the issue eorn pointed out that the GWT version is incorrect.

rkelly commented on 2017-09-25 14:00

I'm getting errors when trying to run since boost and boost-libs have been updated to 1.65.1-1.

rstudio: error while loading shared libraries: libboost_date_time.so.1.64.0: cannot open shared object file: No such file or directory

rstudio does run if boost & boost-libs are downgraded back to 1.64.

eorn commented on 2017-09-25 06:46

It looks like changing line 6 of the PKGBUILD works:

from
"_gwtver=2.7.0"
to
"_gwtver=2.8.1"

kieto commented on 2017-09-23 17:30

Hi, I have tried compiling this package running "makepkg -sci", but for me and other IRC users, the following error appears: https://ptpb.pw/gKku

hwkiller commented on 2017-06-15 19:23

I'm once again stealing a bit of your PKGBUILD (full disclosure). The rstudio team recently changed their dependencies/common/install-* scripts to see whether you're on ubuntu, suse, or centos, and if you're not on those, it'll throw an error. Your script circumvents that by including pandoc as a dependency and symlinking to the correct directories. This approach fixes the issue, presumably, and so I'm putting your prepare() statements into the rstudio-server-git's pkgbuild.

I assume if this works for the desktop release, it should work for the server release. One thing I noticed though, is that you don't do anything with the dictionaries.
I installed rstudio-server using your prepare statement (and the hunspell-en dependency), but in rstudio-server, it fails to find any dictionaries and throws errors related to hunspell at runtime. So for the time being, I'm using the ./install-dictionaries script.

hwkiller commented on 2017-06-15 02:41

I think this package will now require qt5-webkit-ng for a while. Updated recently, and rstudio crashes. I replaced qt5-webkit with qt5-webkit-ng, and it is working again.

I think the next qt5 release will include the patches from qt5-webkit-ng, so reverting back to qt5-webkit should be fine afterward.

laoshanlong commented on 2017-05-26 21:06

Fails to build, requires libgfortran.so.4, but I have libgfortran.so.3 and have no idea what to do.

/usr/lib64/R/bin/exec/R: error while loading shared libraries: libgfortran.so.4: cannot open shared object file: No such file or directory
==> ERROR: A failure occurred in prepare().
Aborting...

hwkiller commented on 2017-05-01 23:27

Nevermind. I resolved it. Had to include both the socketproxy-openssl.patch along with a new patch of mine that:
- Changes a reference to <openssl> to <openssl-1.0>
- Changes cmake to forcefully use the libcrypto.so and libssl.so in /usr/lib/openssl-1.0

They don't make this easy.

hwkiller commented on 2017-05-01 19:44

Indeed, thank you for that. I was racking my brain over why my rstudio-server-git package wasn't building.

I'm guessing, though I'm not sure, that this has something to do with the update to openssl from 1.0 to 1.1. I couldn't figure out how to add openssl-1.0 to the cmake system, but even after an hour of trying, it was still failing to build at the same point.

I'm currently trying to apply a patch directly on the .cpp as you did to use openssl-1.0 rather than openssl 1.1; any help you could provide would be very appreciated.

artemklevtsov commented on 2017-04-28 05:23

@dlin many thanks for this.