![]() ![]() # If you want to use remove.packages() at this point it's fine. You can accomplish #1 (which is probably safest in various conditions) by this sequence: # In original installation, get the non-default package list: It has worked for me in a Mac, but I have not seen a promise in the R Installation and Administration Guide or the R FAQ that it should work. I'm going to back off from endorsing #3 if you are moving any of the base R installation. It is often the case that new versions add requirements (such as the impending requirement in 2.14.x for NAMESPACEs).Įdit: Seeing this is just moving around the deck chairs. In this manner the packages that need to be rebuilt for new versions will get updated. but if and only if you then run: update.packages(checkBuilt=TRUE) Option #3 (copying old library to new library) should work. I'm not upgrading R, but Dirk Eddelbuettel's suggestion of not installing packages in the filetree of R is wise. UPDATE 2: Answers to another SO post have some good ideas on how to avoid this problem when upgrading. It seems that if it is necessary to update or reinstall all packages in order to be sure things are installed correctly, then that is a path more akin to option #1 than option #3. Updating R or the packages may be done separately, but the question is just whether or not moving the libraries is feasible. UPDATE 1 / Clarification: Just to clarify: I am only migrating libraries, not changing the version of R or the versions of the packages. Naturally, just the libraries (directories) are moved, but packages could be affected. (*) There are several libraries and many scores of packages. This isn't a library problem per se, but it is one indication of a package (and a good package at that) keeping a private copy of an absolute path. Regarding the storage of absolute paths, I found that rJava stores the location of R_HOME in a file called run. Is #3 safe or are there serious problems with it? The issues I've identified are: directory permissions and the possibility that any package's setup stores absolute paths rather than relative paths (which seems unsound and unnecessary). Option #2 should work, but seems a bit unsound. ![]() Library.site in R_HOME/etc/Rprofile.site, as suggested in the R Installation and Administration manual Use the mv command in Linux to move the directories wholesale and update.Move the libraries (directories) using mv and use symlinks to point to the new locations (and eventually remove the symlink).Run remove.packages() for all of the non-base packages, and install anew via install.packages(lib = "/path/to/new/location").libPaths() and have looked through the "R Installation and Administration" manual to find out about migrating libraries, but don't see a recommended process. I realize that the locations of libraries are identified via. Also, it’s been a few years since I last looked at Jabref and it’s really impressive how much it’s advanced.I'd like to move several R libraries (*) from one drive to another, on Linux, and would like to know whether a simple move is feasible and safe or if I should uninstall and reinstall the packages. Is it possible to have JR change the name of the associated files to reflect the new key? I understand how to make it name files for NEW entries according to the bibtexkey, but not if I can rename files when the bibtexkey changes. Once I’ve solved point 1, I will change the bibtexkey for all of the articles (JR can’t automatically create keys using the scheme I used in BD). What is the best way to mass associate the remaining PDFs with their entries? I’m thrown by the range of options in the Quality menu that refer to file links. bib file, some of the entires are linked to their PDFs, but most aren’t. bib file and named according to the Bibtexkey. They are all in subfolders of the folder holding the. bib file, I have about 6000 associated PDFs (I know…). I apologize if these questions seem very basic, but I’m still struggling to shift my mind-set from how BD does things.Īlong with the. I’m moving from Bibdesk to Jabref and hope for a little help. ![]()
0 Comments
Leave a Reply. |