Package Details: rstudio-server-git v2022.02.3+492.r1692.g7faaa81408-1

Git Clone URL: https://aur.archlinux.org/rstudio-server-git.git (read-only, click to copy)
Package Base: rstudio-server-git
Description: A new integrated development environment (IDE) for R programming language
Upstream URL: http://www.rstudio.org/
Licenses: AGPL3
Conflicts: rstudio-server
Submitter: None
Maintainer: nobodyinperson
Last Packager: nobodyinperson
Votes: 9
Popularity: 0.000000
First Submitted: 2012-08-02 13:07 (UTC)
Last Updated: 2022-08-01 18:10 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

hwkiller commented on 2019-10-08 03:17 (UTC)

@xia0er, You probably won't see a big performance bump. Aside from being on the bleeding edge, compiling from source using native optimizations could speed things up, but I doubt rstudio, per se, is where any bottleneck lies.

xia0er commented on 2019-10-08 00:46 (UTC) (edited on 2019-10-08 00:55 (UTC) by xia0er)

Besides being on the bleeding edge of the code (and possible goodies that are yet available in the released version), is there an advantage of this package (built from source) over rstudio-server-bin (using the deb package shipped by R Studio)? Basically I'd like to know whether rstudio-server would see any performance bump when built from source on an archlinux box? Thanks!

hwkiller commented on 2019-09-23 20:35 (UTC)

@mehrad:

That's unsupported behavior in general. You can modify the PKGBUILD file to not require R yourself. Just remove it from the dependencies array. It will probably work.

mehrad commented on 2019-09-03 21:00 (UTC)

@hwkiller I have installed multiple R versions on my system and at any given time, one of them is symlinked to /usr/bin/R to be used as the default R version. None of these R installations were done through pacman and I have compiled them myself.

Using the official Github repo of Rstudio, the installation process does not force the user to have R installed through pacman, but using your AUR, I am forced to install R despite the fact that I already have R and it is symlinked properly as which R shows.

is it possible to get rid of such restriction from your AUR?

junda commented on 2019-04-08 20:00 (UTC)

It seems that the package now requires gwt-2.8.2 to build. Please update _gwtver to 2.8.2

hwkiller commented on 2018-06-17 23:24 (UTC)

Just an FYI; upstream just resolved the latest issues. It should compile fine from master now.

hwkiller commented on 2018-05-08 23:13 (UTC)

Don't mark this out of date, people. It's a git package; the version number here means nothing, and is auto-generated.

hwkiller commented on 2018-04-10 19:01 (UTC)

@tealeaf,

There are actually two errors. The SSL one is probably an easier fix as you've mentioned. I think that's just a carry-over from SSL1.0.

The first error is harder, and I can't figure out why it's happening. It has something to do with AsyncClientSsl's constructor, but I see nothing wrong with it; but then - I'm not very well versed in C++. It seems like the issue is with the constructor's first initialization item, even though the error message specifies verify_(verify).

tealeaf commented on 2018-04-09 19:35 (UTC) (edited on 2018-04-09 19:36 (UTC) by tealeaf)

I noticed! :)

Hmm. I wonder if the patch they applied for other old SSL code would work in the same place: https://github.com/rstudio/rstudio/issues/1855 -- the specific code is here: https://github.com/rstudio/rstudio/pull/1894/files

I'll have a play with patching the git version here and see if it works.

hwkiller commented on 2018-04-09 16:12 (UTC) (edited on 2018-04-09 16:12 (UTC) by hwkiller)

@tealeaf; Yes, I am actually the one that filed that bug. It seems like they've been changing the async TCP connection code, and they included code that hasn't been touched for three years. That three year old code used ssl 1.0, and I'm guessing this needs to be updated.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »