-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
instal.packages('anything') just hangs forever #19
Comments
This is SELinux blocking your manually-installed package. If you disable SELinux, it will work. But I don't recommend it. I'll package Anyway, my recommendation is to use the iucar/cran Copr repo. The |
Ok, thanks, unless I misunderstand something my setup is vanilla so it might be worth addin a line in the REAME.md. |
Sure, I'll add a warning about SELinux...
... and about this. With iucar/cran and CoprManager, you have access to almost the whole CRAN, so IMO there's no point in installing
No, there isn't.
Not sure if I follow. With |
Hello, with regards to root I mean that for me the packages installed with CoprManager are installed in /usr/local/lib/R/library and are owned by root. I do not think that would be something I'd be able to do at work. |
Yes, and another advantage of this is that a system with e.g. 15 users don't have 15 installations of probably outdated versions of hundreds of packages. I think this is an advantage for sysadmins: if they activate the Copr repo and enable CoprManager, all users will be installing (without root privileges) and sharing packages under /usr/local/lib/R/library, and the sysadmin can ensure that they are up-to-date. |
True but at the same time I think most companies will have parallel install
for different version of R. I do not think you want people sharing
libraries ie. some users updating packages that other would like to keep as
is.
Best setup (in my view) is multiple installs with large system libraries
(per version) shared by multiple users and local libraries for personal
use. But using bspm in this setup would require the possibility of
specifying some kind of —prefix for installation.
…On Tue, 1 Sep 2020 at 20:24, Iñaki Ucar ***@***.***> wrote:
Yes, and another advantage of this is that a system with e.g. 15 users
don't have 15 installations of probably outdated versions of hundreds of
packages. I think this is an advantage for sysadmins: if they activate the
Copr repo and enable CoprManager, all users will be installing (without
root privileges) and sharing packages under /usr/local/lib/R/library, and
the sysadmin can ensure that they are up-to-date.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3R6ON22YOUKW2NAXVZEZLSDVC6BANCNFSM4QPAAR6A>
.
|
Not really: |
Already compatible with this setup if not used by non admin users right (as
bspm will not install in USER_LIBS) ? Else I am not following :\
…On Tue, 1 Sep 2020 at 21:11, Iñaki Ucar ***@***.***> wrote:
Not really: bspm does not decide the installation directory; R does. So
it is already compatible with the setup you are describing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3R6OMOOE25LKPAGLNDDI3SDVIPXANCNFSM4QPAAR6A>
.
|
I am saying that, if you have multiple R installations from multiple system repos, each repo with its own packages and stuff, then bspm can pull them out in their different installation paths. What you cannot expect, of course, is that from a single system repository, anyone would be able to pull out those binary packages to different instalation directories and magically convert them to different versions of R. But that's not bspm's limitation, that's how system repositories work. |
Ok sure that’s well understood.
Regards
…On Wed, 2 Sep 2020 at 09:13, Iñaki Ucar ***@***.***> wrote:
I am saying is that, if you have multiple R installations from multiple
system repos, each repo with its own packages and stuff, then bspm can pull
them out in their different installation paths.
What you cannot expect, of course, is that *from a single system
repository*, anyone would be able to pull out those binary packages to
different instalation directories *and* magically convert them to
different versions of R. But that's not bspm's limitation, that's how
system repositories work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3R6OKND37JCRHPLD4NQY3SDX5CZANCNFSM4QPAAR6A>
.
|
(BTW I'm keeping this open for me to remember to add something to the README. Thanks for the discussion!) |
Hello, I gave a try to bspm without success.
Here is what I did
I install bspm as root
=> that worked fine
I made sure I had all required deps
Then in R
=> there is hangs forever
The text was updated successfully, but these errors were encountered: