You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Jonathan Keane (Jira)" <ji...@apache.org> on 2021/03/17 21:01:00 UTC
[jira] [Created] (ARROW-12008) [R] [Packaging] Developing +
{LIBARROW_BINARY=true}
Jonathan Keane created ARROW-12008:
--------------------------------------
Summary: [R] [Packaging] Developing + {LIBARROW_BINARY=true}
Key: ARROW-12008
URL: https://issues.apache.org/jira/browse/ARROW-12008
Project: Apache Arrow
Issue Type: Improvement
Components: Packaging, R
Reporter: Jonathan Keane
As far as I can tell from reading configure + nixlibs.sh, if one tries to use {LIBARROW_BINARY=true}} on a source checkout there really isn't a binary to be found to install. The installation process does mention that a binary isn't found + it will build from source.
I don't know that we need to support installing a binary from a development branch (afterall, it's entirely possible libarrow would no longer be compatible with the r package) but I think we should fail a little bit more loudly (or express that the binary install will not be attempted because it looks like one is building from a source checkout (possibly detected by seeing if the version is ~x.x.x.9000)).
Alternatively, we could add date-guessing and attempt to download the nightly libarrow corresponding to that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)