search for: packnam

Hi, trying to install a package containing C code and requiring non-default configure argument settings the incantation (this has worked for R <= 2.8.1 on the same architectures) R CMD INSTALL --configure-args="--with-opt1 --with-opt2" packname does always result in a warning Warning: unknown option '--with-opt2' and consequently the option is ignored. Reverting the order of options results in the now last option to be ignored. Alternative quoting has not provided a solution. Using R CMD INSTALL --configure-args=--with-opt1 -...

...;t trust the filename that is sent by the remote server, and uses only the filename extracted from the URL. Without extension, RPM doesn't know how to unpack the sources. So we have to do the following similarly odd trick (note the "#"): Source0: https://cran.r-project.org/package=%{packname}&version=%{version}#/%{packname}_%{version}.tar.gz Did you consider this problem? Is there any alternate immutable URL *with* extension? If not, is there any potential issue with the trick above? Regards, -- I?aki Ucar

...t by the remote server, > and uses only the filename extracted from the URL. > > Without extension, RPM doesn't know how to unpack the sources. So we > have to do the following similarly odd trick (note the "#"): > > Source0: > https://cran.r-project.org/package=%{packname}&version=%{version}#/%{packname}_%{version}.tar.gz > > Did you consider this problem? Is there any alternate immutable URL > *with* extension? If not, is there any potential issue with the trick > above? > > Regards, > -- > I?aki Ucar > > _________________________...

Hello, I hope the is the right list to send this suggestion to. I was wondering if it might be possible to have CRAN store the most current version of a package's source tarball at a location that does not change. As an example, the source tarball for `httr` is stored at https://cran.r-project.org/src/contrib/httr_1.3.1.tar.gz. However, once the next version of `httr` is released, the URL for