[
https://issues.apache.org/jira/browse/ARROW-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538898#comment-16538898
]
Wes McKinney commented on ARROW-2792:
-------------------------------------
Uploading a tarball for each task seems reasonable. Since the deployment code
is somewhat opaque for this
https://github.com/apache/arrow/blob/master/dev/tasks/python-wheels/travis.linux.yml#L49,
the tasks themselves would need to determine whether the set of produced
artifacts is complete before uploading to GitHub
> [Packaging] Consider uploading tarballs to avoid naming conflicts
> -----------------------------------------------------------------
>
> Key: ARROW-2792
> URL: https://issues.apache.org/jira/browse/ARROW-2792
> Project: Apache Arrow
> Issue Type: Task
> Components: Packaging
> Reporter: Krisztian Szucs
> Priority: Major
> Fix For: 0.10.0
>
>
> [~kou] has suggested, that we should upload tarballs for linux package
> builds, to include all .deb and/or .rpm packages.
> For conda packages currenlty we postfix the artifacts with the arch name to
> avoid naming conflicts. To remain consistent we should chose one of the
> strategies (postifx or tarballs) and apply for each tasks.
> However tarballs would be a trivial solution to resolve naming conflicts,
> ensuring that a tarball contains all of the expected artifacts would require
> to download and extract it beforehand. This requires changes in status checks
> and artifact downloading / signing.
> [~cpcloud] thoughts?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
