[Rd] Improving messaging on successful binary package installation
I have been testing R-devel and really enjoying fast parallel
downloading of R packages, especially on mac/win where there is no
complication step either, it is super nice.
Perhaps the install.packages() messaging could still be improved a
bit. Right now if one installs a package on Windows/MacOS we see:
> install.packages('V8')
also installing the dependency ‘Rcpp’
trying URL
'https://cloud.r-project.org/bin/macosx/big-sur-arm64/contrib/4.5/Rcpp_1.0.14.tgz'
trying URL
'https://cloud.r-project.org/bin/macosx/big-sur-arm64/contrib/4.5/V8_6.0.0.tgz'
The downloaded binary packages are in
/var/folders/46/wtyv3f9n7g1657wntpn0cl54gn/T//RtmpMd0YSV/downloaded_packages
In the above output, there is no confirmation that the package
installation was successful. Instead we get a message that download
binary packages are to be found in a temporary directory, making it
seem as if the user has to do something with this? This is confusing.
Perhaps the messaging could be improved by not showing this tempir.
Instead install.packages() could end with a short success summary
like:
Successfully installed packages 'V8', 'Rcpp' in
/Library/Frameworks/R.framework/Versions/4.5-arm64/Resources/library
Or we could not show any directory at all. But at least the user knows
installation has succeeded.
While we're at it, the phrasing "trying URL" is a bit odd, both words
are redundant in this context. Maybe it can just be replaced by
"Downloading"
These are silly details but I think they make a difference especially
to novice users.
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Improving messaging on successful binary package installation
On 1/29/25 15:27, Jeroen Ooms wrote:
I have been testing R-devel and really enjoying fast parallel
downloading of R packages, especially on mac/win where there is no
complication step either, it is super nice.
Perhaps the install.packages() messaging could still be improved a
bit. Right now if one installs a package on Windows/MacOS we see:
> install.packages('V8')
also installing the dependency ‘Rcpp’
trying URL
'https://cloud.r-project.org/bin/macosx/big-sur-arm64/contrib/4.5/Rcpp_1.0.14.tgz'
trying URL
'https://cloud.r-project.org/bin/macosx/big-sur-arm64/contrib/4.5/V8_6.0.0.tgz'
The downloaded binary packages are in
/var/folders/46/wtyv3f9n7g1657wntpn0cl54gn/T//RtmpMd0YSV/downloaded_packages
In the above output, there is no confirmation that the package
installation was successful. Instead we get a message that download
binary packages are to be found in a temporary directory, making it
seem as if the user has to do something with this? This is confusing.
You may have forgotten to mention above that the output also says:
package 'V8' successfully unpacked and MD5 sums checked
which means the installation was successful.
Tomas
Perhaps the messaging could be improved by not showing this tempir.
Instead install.packages() could end with a short success summary
like:
Successfully installed packages 'V8', 'Rcpp' in
/Library/Frameworks/R.framework/Versions/4.5-arm64/Resources/library
Or we could not show any directory at all. But at least the user knows
installation has succeeded.
While we're at it, the phrasing "trying URL" is a bit odd, both words
are redundant in this context. Maybe it can just be replaced by
"Downloading"
These are silly details but I think they make a difference especially
to novice users.
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] 87668 fails on Windows 10 with "pdflatex not found"
Am 29.01.25 um 20:20 schrieb Avraham Adler: I see there have been a number of tweaks to the document build recently (87650, 87654, 87658, 97660, 97661, etc.) To Rd2pdf, yes, mostly bug fixes for some rare usages. Some more changes are in the making, also for texi2pdf (but that has not been touched yet). I tried building 87668 today on Windows 10 and received the error below. Is this related? Thanks for checking, it shouldn't be. I doubt the error is related to the Rd2pdf changes as that isn't involved in building the vignettes. You could try an older revision or maybe R-patched or render a minimal LaTeX document using tools::texi2pdf(), to see if the error isn't just related to your LaTeX setup. The error suggests that whatever program is set to be PDFLATEX on your system, usually pdflatex, cannot be found: smells like a PATH issue. Best regards, Sebastian Meyer Thank you, Avi building/updating vignettes for package 'grid' ... processing 'displaylist.Rnw' Error: compiling TeX file 'displaylist.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'parallel' ... processing 'parallel.Rnw' Error: compiling TeX file 'parallel.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error: running Sweave on vignette 'C:/RDevel/avraham/R/trunk/src/library/utils/vignettes/Sweave.Rnw' failed with message: chunk 2 Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : pdflatex is not available Execution halted make[2]: *** [Makefile.win:99: vignettes] Error 1 make[1]: *** [Makefile:345: vignettes] Error 2 make: *** [Makefile:395: distribution] Error 2 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] 64bit integers
Hi everyone, Thank you all for responding to my question. I appreciate it. Kind regards, Tony Van: Prof Brian Ripley Verzonden: zondag 26 januari 2025 09:05 Aan: Simon Urbanek ; Tony Wilkes CC: r-devel@r-project.org Onderwerp: Re: [Rd] 64bit integers On 25/01/2025 23:37, Simon Urbanek wrote: > Tony, > > Dirk sent a good response. I would like to add to that that it goes beyond > just bits in SEXP: adding a new type involved in arithmetics is not only a > lot of work but has performance implications. Also it is unclear how it > should behave in the int32_t, double, int64_t triangle of vector classes in > that respect (they don't nest) while retaining compatibility (doubles promote > because they are a superset, but int64_t cannot do that). I am yet to see a > real use-case where 53-bits are not sufficient in integer arithmetics so it > is unclear that opening that big can of worms (and breaking things) would > have any benefit. Typically, the only use-case for full 64-bit integers is as > opaque 64-bit storage (e.g., randomly generated IDs) but there arithmetics > make no sense there and packages are already covering that need. Both Luke and I have looked into 64-bit integers, and not yet found them a high enough priority. Perhaps the most compelling motivation has not yet been mentioned. Array dimensions (especially of matrices) and hence indices are restricted to 2^31-1, although total array size is limited by available storage. If we support more, people will expect to do matrix operations on such matrices, and that is going to need versions of e.g. LAPACK which work with 64-bit integers. Modern Fortran allows different INTEGER sizes to interwork, but most of the matrix code is not written in modern Fortran. If compiling them from source it would likely be possible to include both 32-bit and 64-bit matrix libraries, but this will be tricky at best with enhanced BLAS/LAPACK which often do have both 32- and 64-bit versions but using the same entry-point names. Ironically there were versions of S-PLUS with 64-bit integers. But only 64-bit integers as in S pointers and integers had to be the same size. That is not something we could contemplate for R, as vast numbers of packages assume that R's integers map to C int (tested to be 32-bit) and Fortran 32-bit INTEGER. > > Cheers, > Simon > > >> On Jan 25, 2025, at 11:08 PM, Tony Wilkes wrote: >> >> Hi everyone, >> >> I heard somewhere that Core R is developing the implementation of true 64bit >> integers. >> Is this true? If so, may I know what the status is of this development, and >> when, approximately, one can expect 64bit integers to be available in R? It would have been helpful to tell us what you wanted to do with them. >> Thank you for your time! >> >> Kind regards, >> >> Tony -- Brian D. Ripley, rip...@stats.ox.ac.uk Emeritus Professor of Applied Statistics, University of Oxford [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Improving messaging on successful binary package installation
Other people may be like me where R is the first programming language I
learned.
It took probably ~5/6 years or more to learn what “MD5” is and even longer
to understand what a checksum is and why they’re useful.
I think saying it _explicitly_ is helpful. Maybe saying that 1) the package
was installed and 2) it was verified could be a nice balance
On Wed, Jan 29, 2025 at 07:34 Tomas Kalibera
wrote:
>
> On 1/29/25 15:27, Jeroen Ooms wrote:
> > I have been testing R-devel and really enjoying fast parallel
> > downloading of R packages, especially on mac/win where there is no
> > complication step either, it is super nice.
> >
> > Perhaps the install.packages() messaging could still be improved a
> > bit. Right now if one installs a package on Windows/MacOS we see:
> >
> >> install.packages('V8')
> >also installing the dependency ‘Rcpp’
> >trying URL '
> https://cloud.r-project.org/bin/macosx/big-sur-arm64/contrib/4.5/Rcpp_1.0.14.tgz
> '
> >trying URL '
> https://cloud.r-project.org/bin/macosx/big-sur-arm64/contrib/4.5/V8_6.0.0.tgz
> '
> >The downloaded binary packages are in
> >
> /var/folders/46/wtyv3f9n7g1657wntpn0cl54gn/T//RtmpMd0YSV/downloaded_packages
> >
> >
> > In the above output, there is no confirmation that the package
> > installation was successful. Instead we get a message that download
> > binary packages are to be found in a temporary directory, making it
> > seem as if the user has to do something with this? This is confusing.
>
> You may have forgotten to mention above that the output also says:
>
> package 'V8' successfully unpacked and MD5 sums checked
>
> which means the installation was successful.
>
> Tomas
>
> >
> > Perhaps the messaging could be improved by not showing this tempir.
> > Instead install.packages() could end with a short success summary
> > like:
> >
> >Successfully installed packages 'V8', 'Rcpp' in
> >
> /Library/Frameworks/R.framework/Versions/4.5-arm64/Resources/library
> >
> > Or we could not show any directory at all. But at least the user knows
> > installation has succeeded.
> >
> > While we're at it, the phrasing "trying URL" is a bit odd, both words
> > are redundant in this context. Maybe it can just be replaced by
> > "Downloading"
> >
> > These are silly details but I think they make a difference especially
> > to novice users.
> >
> > __
> > R-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-devel
>
> __
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>
[[alternative HTML version deleted]]
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] 87668 fails on Windows 10 with "pdflatex not found"
I see there have been a number of tweaks to the document build recently (87650, 87654, 87658, 97660, 97661, etc.) I tried building 87668 today on Windows 10 and received the error below. Is this related? Thank you, Avi building/updating vignettes for package 'grid' ... processing 'displaylist.Rnw' Error: compiling TeX file 'displaylist.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'parallel' ... processing 'parallel.Rnw' Error: compiling TeX file 'parallel.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error: running Sweave on vignette 'C:/RDevel/avraham/R/trunk/src/library/utils/vignettes/Sweave.Rnw' failed with message: chunk 2 Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : pdflatex is not available Execution halted make[2]: *** [Makefile.win:99: vignettes] Error 1 make[1]: *** [Makefile:345: vignettes] Error 2 make: *** [Makefile:395: distribution] Error 2 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] 87668 fails on Windows 10 with "pdflatex not found"
The builder runs tools::texi2pdf() on the vignettes. Does that give the same error for you? Do earlier revisions work? Duncan Murdoch On 2025-01-29 2:20 p.m., Avraham Adler wrote: I see there have been a number of tweaks to the document build recently (87650, 87654, 87658, 97660, 97661, etc.) I tried building 87668 today on Windows 10 and received the error below. Is this related? Thank you, Avi building/updating vignettes for package 'grid' ... processing 'displaylist.Rnw' Error: compiling TeX file 'displaylist.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'parallel' ... processing 'parallel.Rnw' Error: compiling TeX file 'parallel.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error: running Sweave on vignette 'C:/RDevel/avraham/R/trunk/src/library/utils/vignettes/Sweave.Rnw' failed with message: chunk 2 Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : pdflatex is not available Execution halted make[2]: *** [Makefile.win:99: vignettes] Error 1 make[1]: *** [Makefile:345: vignettes] Error 2 make: *** [Makefile:395: distribution] Error 2 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] 87668 fails on Windows 10 with "pdflatex not found"
Sorry, that misses a step. You should try R CMD Sweave --pdf displaylist.Rnw which runs it through Sweave to make displaylist.tex and then tries to run texi2pdf() on that. Duncan Murdoch On 2025-01-29 3:00 p.m., Duncan Murdoch wrote: The builder runs tools::texi2pdf() on the vignettes. Does that give the same error for you? Do earlier revisions work? Duncan Murdoch On 2025-01-29 2:20 p.m., Avraham Adler wrote: I see there have been a number of tweaks to the document build recently (87650, 87654, 87658, 97660, 97661, etc.) I tried building 87668 today on Windows 10 and received the error below. Is this related? Thank you, Avi building/updating vignettes for package 'grid' ... processing 'displaylist.Rnw' Error: compiling TeX file 'displaylist.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'parallel' ... processing 'parallel.Rnw' Error: compiling TeX file 'parallel.tex' failed with message: pdflatex is not available Execution halted building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error: running Sweave on vignette 'C:/RDevel/avraham/R/trunk/src/library/utils/vignettes/Sweave.Rnw' failed with message: chunk 2 Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : pdflatex is not available Execution halted make[2]: *** [Makefile.win:99: vignettes] Error 1 make[1]: *** [Makefile:345: vignettes] Error 2 make: *** [Makefile:395: distribution] Error 2 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
