> Hervé Pagès writes:
> FWIW NeedsCompilation is a misnomer. IIRC when I was discussing this
> feature with R core members many years ago, it doesn't only flag
> packages that require compilation (and thus contain arch-specific binary
> files), but it is more generally intended to flag pack
This is all a bit above my head but as a Windows user I have always
interpreted NeedsCompilation as meaning I could install it without
having to wait for binaries to appear on CRAN. I do not need Rtools for
my own packages so I have never installed it.
Michael
On 17/05/2025 09:13, Iñaki Ucar
On 17 May 2025 at 10:13, Iñaki Ucar wrote:
| El sáb., 17 may. 2025 4:03, Hervé Pagès
| escribió:
|
| > FWIW NeedsCompilation is a misnomer. IIRC when I was discussing this
| > feature with R core members many years ago, it doesn't only flag
| > packages that require compilation (and thus contai
El sáb., 17 may. 2025 4:03, Hervé Pagès
escribió:
> FWIW NeedsCompilation is a misnomer. IIRC when I was discussing this
> feature with R core members many years ago, it doesn't only flag
> packages that require compilation (and thus contain arch-specific binary
> files), but it is more generally
FWIW NeedsCompilation is a misnomer. IIRC when I was discussing this
feature with R core members many years ago, it doesn't only flag
packages that require compilation (and thus contain arch-specific binary
files), but it is more generally intended to flag packages that the user
wouldn't be abl
On Thu, 15 May 2025 at 11:42, Jeroen Ooms wrote:
>
> On Wed, May 14, 2025 at 11:05 PM Simon Urbanek
> wrote:
> >
> > Can you give an example, please? I wonder if there is a real use-case or
> > just bad package design.
>
> The case that bit me yesterday was a Bioconductor package Rigraphlib,
> s
On 15 May 2025 at 11:41, Jeroen Ooms wrote:
| The case that bit me yesterday was a Bioconductor package Rigraphlib,
| see
https://bioconductor.org/packages/release/bioc/src/contrib/Rigraphlib_1.0.0.tar.gz
|
| This package builds a static library entirely from a configure script.
| Because there
On Wed, May 14, 2025 at 11:05 PM Simon Urbanek
wrote:
>
> Jeroen,
>
> thanks for raising the issues. Comments inline.
>
>
> > On May 15, 2025, at 1:47 AM, Jeroen Ooms wrote:
> >
> > R-universe builds and checks all CRAN packages on arm64 on Mac, Linux
> > and soon Windows. It is important that we
> Simon Urbanek writes:
Re part II (CRAN packages which have NeedsCompilation: yes but don't
really need it): I of course have code for this, last touched in 2016.
Running the code (which currently only looks at having a 'src' subdir,
based on one possible interpreation of
it is normally s
Jeroen,
thanks for raising the issues. Comments inline.
> On May 15, 2025, at 1:47 AM, Jeroen Ooms wrote:
>
> R-universe builds and checks all CRAN packages on arm64 on Mac, Linux
> and soon Windows. It is important that we can identify from a binary
> package for which architecture it was bui
Strongly in favour of Jeroen's suggestions. Thanks for putting them together.
Iñaki
On Wed, 14 May 2025 at 15:48, Jeroen Ooms wrote:
>
> R-universe builds and checks all CRAN packages on arm64 on Mac, Linux
> and soon Windows. It is important that we can identify from a binary
> package for whi
11 matches
Mail list logo