[
https://issues.apache.org/jira/browse/ARROW-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565646#comment-16565646
]
Phillip Cloud commented on ARROW-2959:
--------------------------------------
Unless we're actually testing this, the expectation to keep the script cross
platform without making it known what systems this needs to run on _and_
without providing a way for people to easily test across these platforms is
unreasonable IMO.
Just to be clear, I personally am not going to invest time in bending over
backwards to keep the script cross-undocumented-system compatible. I'm not
going to stress out about keeping it that way for systems whose setup I have no
way to reproduce.
I wasted a lot of time today only to figure out that the verification script
can fail with a segfault when you are in a conda environment and have
{{ARROW_HOME}} set. I don't think documenting this solves the problem, though
it would have solved my immediate problem.
What is reasonable to me and what I think would solve the problem, is to
provide a reliable way to set up each system we expect to be able to run on so
that anyone can verify all supported platforms with minimal hassle.
Is there an alternative to docker for solving this problem in a way that is
acceptable to everyone?
> Dockerize verify-release-candidate.{sh,bat}
> -------------------------------------------
>
> Key: ARROW-2959
> URL: https://issues.apache.org/jira/browse/ARROW-2959
> Project: Apache Arrow
> Issue Type: Task
> Components: C++, Packaging
> Affects Versions: 0.9.0
> Reporter: Phillip Cloud
> Priority: Major
>
> There are a number of issues with the linux version of this script that would
> disappear if the commands were all being run in a docker container.
> Anyone with docker installed should be able to verify the release candidate
> We could probably do the same for windows as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
