R SIG Debian - Aug 2021 - Configure error: checking if libcurl supports https... no

Rolf,

I am truly sorry but I am getting lost in your original message. Could you
follow-up and describe (concisely, if possible) what your question is?  Is it
 - installing 4.1.1 or 4.1.0
 - developing a package of yours
 - installing a package ?

You seem to interweave a few strands in ways that make it less clear exactly
what is holding you back.

On 29 August 2021 at 15:11, Rolf Turner wrote:
| > So maybe my preference is on the wrong side of the tracks too. I
| > don't fully understand why these cannot coexist...
| 
| Sheesh!  If *you* don't understand, what hope is there for the rest of
| us, me in particular?

Sometimes it is a simple lack of resources / time / effort / merit. Something
I meant to tackle is to allow r-base-core to coexist with a (to be written
package) r-base-devel but doing that _cleanly_ with the expect robustness is
a lot of work so I have yet to do it, even after ~ 20 years of working on R
and the r-{base,doc}-* packages as well as many r-cran-* ones.

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

On Sat, 28 Aug 2021 22:33:08 -0500
Dirk Eddelbuettel <edd at debian.org> wrote:
> 
> Rolf,
> 
> I am truly sorry but I am getting lost in your original message.
> Could you follow-up and describe (concisely, if possible) what your
> question is?  Is it
>  - installing 4.1.1 or 4.1.0
>  - developing a package of yours
>  - installing a package ?
Sorry if I over-egged my explanation.

* I am trying to install R 4.1.0 (the previous version of R).
  I have the current version, R 4.1.1 (readily available as a Linux
  binary) up and going; no problema.

* My desire to install 4.1.0 was *motivated* by a strange
  conundrum with respect to a package that I am developing.
  But that's *not* actually relevant at the moment.

* I successfully downloaded the source for R 4.1.0 and started
  the configure -> make sequence.  But things came to a halt with the
  configure error shown in the subject line.

* I then fooled around with installing/uninstalling various flavours
  of libcurl.dev to see if I could get rid of the configure error.
  Nothing worked.

I hope that my problem is clear now.

cheers,

Rolf

-- 
Honorary Research Fellow
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276