No, don't get in the way of install.packages(). Download the source versions of
the packages and unpack them yourself and fix the source files and update the
DESCRIPTION files. Then follow the instructions in the "Writing R Extensions"
document at the command line (I.e. R CMD check, R CMD build, etc.) to
rebuild/reinstall each package.
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<jdnew...@dcn.davis.ca.us> Basics: ##.#. ##.#. Live Go...
Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...1k
---------------------------------------------------------------------------
Sent from my phone. Please excuse my brevity.
On October 2, 2015 2:39:33 PM PDT, Noel Hunt <noel.h...@gmail.com> wrote:
>I have a few packages for which compilation has
>failed. The errors are simple compile-time errors
>I could fix if the configured source was left
>untouched and not removed.
>
>I have found out how to stop source being removed
>but I want the whole set of extracted, configured files
>left, so I can fix the errors and restart the
>installation.
>
>I haven't found out how to do this; is it possible?
>
> [[alternative HTML version deleted]]
>
>______________________________________________
>R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see
>https://stat.ethz.ch/mailman/listinfo/r-help
>PLEASE do read the posting guide
>http://www.R-project.org/posting-guide.html
>and provide commented, minimal, self-contained, reproducible code.
______________________________________________
R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
